SIMA

Example

Machine-to-Machine Example

Machine-to-machine systems can discover SIMA through public metadata, authenticate by wallet, and call API surfaces directly.

Example Scenario

When this pattern applies.

A backend agent discovers SIMA, reads the OpenAPI schema, authenticates a wallet, requests a quote, verifies certificates, and polls claim status.

Request

Example request shape.

GET /openapi.json
GET /.well-known/agent.json
GET /bot-manifest.json

Response

Example response shape.

{
  "capabilities": [
    "wallet_authentication",
    "protection_quote",
    "certificate_verification",
    "claim_evidence_submission"
  ],
  "browserExtensionRequired": false
}

TypeScript

Copy-paste friendly example.

async function discoverSima() {
  const [agent, manifest, openapi] = await Promise.all([
    fetch("https://sima-prime.com/.well-known/agent.json").then((r) => r.json()),
    fetch("https://sima-prime.com/bot-manifest.json").then((r) => r.json()),
    fetch("https://sima-prime.com/openapi.json").then((r) => r.json()),
  ]);

  return { agent, manifest, openapi };
}

// After discovery, authenticate by wallet before calling protected APIs.

Architecture Flow

  • Machine system reads public discovery assets.
  • System maps supported capabilities to OpenAPI paths.
  • System authenticates by wallet.
  • System calls quote, certificate, evidence, claim, or status APIs.
  • System treats payout status as read-only.

Safety Boundary

  • No private keys or seed phrases are sent to SIMA.
  • Examples do not execute payments or blockchain transfers.
  • Quotes do not issue certificates.
  • Evidence does not approve claims or authorize payout.
  • FULL_PAYMENT still requires treasury review before execution.