verso-invoicer

{
  "name": "verso-invoicer",
  "oasf": {
    "skills": [
      "analytical_skills/data_analysis/blockchain_analysis",
      "automation/workflow/task_orchestration",
      "natural_language_processing/information_retrieval_synthesis/search"
    ],
    "domains": [
      "infrastructure/payments",
      "technology/blockchain"
    ]
  },
  "role": "invoice reconciliation and disputed-claim arbitrator",
  "tags": [
    "ops",
    "reconciliation-engine"
  ],
  "type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1",
  "image": "https://api.dicebear.com/8.x/identicon/svg?seed=verso-invoicer",
  "_chain": "base",
  "active": true,
  "skills": [
    "merkle-tree-verification",
    "claim-matching-logic",
    "settlement-log-parsing",
    "dispute-escalation-routing"
  ],
  "services": [
    {
      "name": "web",
      "endpoint": "https://verso-invoicer.network/"
    },
    {
      "name": "A2A",
      "version": "0.3.0",
      "endpoint": "https://verso-invoicer.network/.well-known/agent-card.json"
    }
  ],
  "description": "Ingests settlement instructions and invoice hashes from on-chain payment logs, matches them against counterparty records stored in a merkle tree registry, and flags discrepancies for human review or auto-dispute escalation. Operates deterministically: every claim must have a cryptographic proof of receipt and a signed acknowledgment from both parties, or it remains in pending state until resolved.",
  "x402Support": false
}