Card snapshot

This is a frozen copy of the agent's agent-card.json as we observed it at the timestamp above. We capture a new snapshot every time the card's content hash changes. Useful for: forensic drift analysis, verifying downstream callers see the right version, reproducing routing decisions made historically.

{
  "name": "AUX Transaction Preflight Agent",
  "description": "Machine-first pre-transaction evidence services: live public OFAC/GLEIF screening, signed evaluation receipts, and a provider-gated bank-destination receipt implementation. Never payment authorization.",
  "supportedInterfaces": [
    {
      "url": "https://aux.prdictionedge.ai/a2a/v1",
      "protocolBinding": "JSONRPC",
      "protocolVersion": "1.0"
    },
    {
      "url": "https://aux.prdictionedge.ai/a2a/v1",
      "protocolBinding": "HTTP+JSON",
      "protocolVersion": "1.0"
    }
  ],
  "provider": {
    "organization": "PrdictionEdge",
    "url": "https://www.prdictionedge.ai"
  },
  "iconUrl": "https://aux.prdictionedge.ai/favicon.svg",
  "version": "0.1.0",
  "documentationUrl": "https://aux.prdictionedge.ai/agents",
  "capabilities": {
    "streaming": false,
    "pushNotifications": false,
    "extendedAgentCard": false
  },
  "defaultInputModes": [
    "application/json"
  ],
  "defaultOutputModes": [
    "application/json"
  ],
  "skills": [
    {
      "id": "transaction-preflight",
      "name": "Transaction Preflight",
      "description": "Evaluate a caller-supplied synthetic B2B payment scenario for duplicate invoices, payment-destination changes, vendor-history anomalies, and signed decision evidence.",
      "tags": [
        "transaction-risk",
        "payment-preflight",
        "duplicate-invoice-detection",
        "payment-destination-change",
        "signed-receipt",
        "synthetic-evaluation"
      ],
      "examples": [
        "Check this synthetic proposed payment for a duplicate invoice before an autonomous agent acts.",
        "Evaluate a synthetic vendor payment after its destination changed and return evidence with the decision."
      ],
      "inputModes": [
        "application/json"
      ],
      "outputModes": [
        "application/json"
      ]
    },
    {
      "id": "mortgage-closing-funds-preflight",
      "name": "Mortgage Closing Funds Preflight",
      "description": "Evaluate a named fictional mortgage closing fixture for destination changes and cash-to-close evidence sufficiency. Never authorizes a wire or accepts real borrower/bank data.",
      "tags": [
        "mortgage-closing",
        "wire-change-detection",
        "cash-to-close",
        "signed-receipt",
        "synthetic-evaluation"
      ],
      "examples": [
        "Evaluate the published wire-change-email fixture and return signed evidence.",
        "Check the closing-match fictional scenario with public FDIC institution context."
      ],
      "inputModes": [
        "application/json"
      ],
      "outputModes": [
        "application/json"
      ]
    },
    {
      "id": "public-business-evidence",
      "name": "Public Business Evidence",
      "description": "Screen a public business name against current official OFAC and GLEIF data. Returns explainable matches, source provenance, a bounded next-step decision, and a signed receipt; never legal clearance or payment authorization.",
      "tags": [
        "ofac",
        "sanctions-screening",
        "gleif",
        "lei",
        "business-identity",
        "public-data",
        "signed-receipt"
      ],
      "examples": [
        "Screen MICROSOFT CORPORATION in the US using OFAC and GLEIF.",
        "Check a public business name for OFAC candidates and return source hashes."
      ],
      "inputModes": [
        "application/json"
      ],
      "outputModes": [
        "application/json"
      ]
    },
    {
      "id": "verified-bank-destination-receipt",
      "name": "Verified Bank-Destination Receipt \u2014 Activation Pending",
      "description": "Correlate institution-returned ACH coordinates with bank-reported owner-name evidence and an active LEI, then issue a signed receipt. Check the receipt's current status before every SEND recommendation. Resolve /api/destination-receipts.json at invocation time; submit bank data only when it reports production_active.",
      "tags": [
        "bank-destination",
        "ach",
        "payee-verification",
        "gleif",
        "signed-receipt",
        "x402",
        "before-send"
      ],
      "examples": [
        "Before recommending SEND, check whether these ACH coordinates match the payee's current signed AUX destination receipt."
      ],
      "inputModes": [
        "application/json"
      ],
      "outputModes": [
        "application/json"
      ]
    },
    {
      "id": "crypto-destination-verification",
      "name": "Crypto-Destination Wallet-Control Evidence",
      "description": "Prove control of a Base, Ethereum, or Solana destination and return a signed receipt with self-published domain and public LEI context. This beta never establishes legal ownership or recommends SEND; it always requires REVIEW.",
      "tags": [
        "crypto-destination",
        "base",
        "usdc",
        "ethereum",
        "solana",
        "wallet-control",
        "payee-verification",
        "signed-receipt",
        "before-send"
      ],
      "examples": [
        "Before recommending a USDC SEND on Base, verify this payee wallet and check the current signed AUX receipt."
      ],
      "inputModes": [
        "application/json"
      ],
      "outputModes": [
        "application/json"
      ]
    },
    {
      "id": "rwa-action-preflight",
      "name": "RWA Action Preflight Evidence Dialogue",
      "description": "Evaluate a BUY, TRANSFER, or ACCEPT action through a machine-to-machine evidence dialogue. AUX gathers public and on-chain evidence, asks targeted questions, accepts agent confirmations or corrections, refreshes material sources, and currently returns signed STOP, REVIEW, or ABORTED. PROCEED_WITH_CONFIRMATION is reserved but disabled until authoritative action-profile adapters exist.",
      "tags": [
        "rwa",
        "tokenized-assets",
        "evidence-dialogue",
        "agent-confirmation",
        "onchain-evidence",
        "gleif",
        "ofac",
        "signed-receipt"
      ],
      "examples": [
        "Before buying this tokenized asset, start an AUX evidence dialogue and continue until the signed bounded decision is ready."
      ],
      "inputModes": [
        "application/json"
      ],
      "outputModes": [
        "application/json"
      ]
    },
    {
      "id": "evidence-claim-evaluation",
      "name": "Evidence and Verification Engine",
      "description": "Evaluate synthetic third-party claims against signed evidence attestations, separating source authority from cryptographic integrity and issuing a revocable signed receipt.",
      "tags": [
        "third-party-claims",
        "evidence-attestations",
        "signed-receipt",
        "revocation",
        "zero-knowledge-ready",
        "synthetic-evaluation"
      ],
      "examples": [
        "Evaluate a published synthetic evidence fixture and return a signed receipt.",
        "Determine whether a signed attestation is authoritative, contradicted, or insufficient."
      ],
      "inputModes": [
        "application/json"
      ],
      "outputModes": [
        "application/json"
      ]
    }
  ]
}