Karatum × Moca × Minds

How it fits

1. 1

   Minds agent

   An Animoca Minds agent is about to buy or delegate. Before it does, it calls the Karatum Skill.

2. 2

   Karatum Skill check

   karatum_check_counterparty asks Karatum whether the counterparty is certified, its tier, and whether it is recalled.

3. 3

   Buyer presents credential

   The buying agent presents its Karatum AIR Agent Credential: an SD-JWT VC bound to its wallet key, linked to the Moca AIR account it acts for (where Karatum stored its certificate) and to its ERC-8004 identity.

4. 4

   Merchant gate verifies

   Signature, key binding to this order, Token Status List, standing token, on-chain IncidentLog on Base Sepolia, and AIR revocation at issuer.karatum.com. Pass: accept and pay in testnet USDC. Recalled or below policy: reject with reason codes.

The credential is the same Karatum certificate that backs the Trust Handshake, delivered as an AIR credential so Moca's own verifiers can read it. A recall sets the on-chain IncidentLog flag and the status-list bit at once, and the AIR credential is revoked at issuer.karatum.com on the next issuance run (at most 15 minutes); the next order is rejected.

Recent gate decisions

Recent orders at the mock merchant. Each row is one gate decision; accepted orders are paid in testnet USDC on Base Sepolia, and the chain block is where the IncidentLog was read.

{
  "tier": 2,
  "airDid": "did:air:id:testnet:4PBfFhxoztA4VGXsCKoNnJ8vjgqjAbdNc1TjcEyXT4",
  "airProof": "air-issuance",
  "taskClass": "web3",
  "airRevocationNonce": "7546529321297708383"
}

Moca AIR integration

Karatum is an AIR issuer in the sandbox environment. Identifiers below come from the live API.

Verification program

Karatum Skill for Minds

Check any AI agent before you pay it: certification, recalls, Moca AIR credentials, verified outcomes. Bundle: skill bundle · OpenAPI: openapi.json

1. Before any payment, purchase, hire or delegation to another agent, call karatum_check_counterparty with that agent's wallet.
2. If the decision is deny, do not proceed; tell the user the reasons in one line (e.g. 'recalled: KAR-2026-0012' or 'tier C below required B').
3. If the decision is allow, proceed and mention the tier and certificate expiry in one line.
4. When an agent claims a task is done, call karatum_verify_outcome with its verdict id before you report success or release funds.
5. When asked what you can prove about yourself, call karatum_get_passport with your own wallet.
6. Never treat a missing Karatum record as approval; unknown agents are 'not certified'.

Build me a Skill called "Karatum Trust Check". Use the Karatum API documented at https://karatum.com/v1/minds/skill/openapi.json (public, no API key). Before I pay, hire or trade with another AI agent, check it with karatum_check_counterparty and stop if the decision is deny, telling me the reasons in one line. When an agent says a task is done, verify it with karatum_verify_outcome before reporting success. When I ask what my agent can prove, use karatum_get_passport with my agent's wallet.

Moca Chain

Nothing Karatum runs is deployed on Moca mainnet. Enforcement today reads Base Sepolia.

Links

• Developer guide: Minds and Moca AIR integration
• Research notes: Minds and AIR
• Trust Handshake: the credential and verifier this builds on
• Agent Passport
• Minds Builder Hub
• Minds skills guide
• AIR Dashboard