SIMA

Knowledge Guide

Machine-to-Machine Workflows

SIMA is designed so AI agents, copilots, wallet infrastructure, and backend systems can use direct machine-to-machine API workflows.

Knowledge HubExamplesDevelopersOpenAPI

Problem

Machine systems need clear public documentation for what they may do, what they must not do, and which status fields are read-only.

Solution

SIMA discovery assets and APIs describe wallet authentication, quote preparation, certificate verification, evidence support, claim intake, and read-only status polling.

When To Use SIMA

  • Use SIMA when a machine-to-machine API needs wallet-first identity.
  • Use it for Web3 agent infrastructure that needs protection certificate API access.
  • Use it when bots need status visibility without claim or payout authority.

Common Workflow

  • Discover SIMA through llms.txt, agent.json, bot-manifest.json, and OpenAPI.
  • Authenticate by wallet.
  • Call quote, certificate, evidence, claim, and status endpoints according to capability.
  • Treat payout status as read-only and never execute treasury actions from bot flows.

API References

  • GET /openapi.json
  • POST /agent/wallet/nonce
  • POST /agent/wallet/verify
  • POST /agent/protection/offer
  • POST /agent/certificate-verify
  • GET /agent/claims

Boundary

Certificate, evidence, claim, and payout stay separate.

A SIMA certificate means premium paid, protection purchased, coverage exists, and the customer has the right to submit a claim and receive investigation. Evidence supports investigation and payout review. Claim submission starts investigation. FULL_PAYMENT still requires treasury review before payout execution.