Developers

Build around the production OpenAPI purchase flow.

OpenAPI is the source of truth. The agent purchase path is live: offer → purchase → payment-intent → confirm-payment → ACTIVE. All commercial amounts are asset-denominated. Install @sima-prime/agent-sdk or call the API directly.

OpenAPI Public Developers Playground LLM Context GitHub SDK Sync Status

Architecture

Wallet-first. Asset-denominated. Certificate-aware.

Humans and agents authenticate by wallet, request a protection offer, purchase coverage, pay premium in SOL, and receive an ACTIVE certificate. Claims and payouts are separate investigation steps — the SDK does not auto-approve them.

Wallet identity

POST /agent/wallet/nonce then POST /agent/wallet/verify. Caller signs outside SIMA.

Protection offer

POST /agent/protection/offer returns asset-denominated commercial terms. Does not collect payment or issue a certificate.

Purchase

POST /agent/protection/purchase with PURCHASE_PROTECTION creates a PENDING_PAYMENT certificate.

Pay and activate

GET payment-intent → caller sends SOL on-chain → POST confirm-payment → ACTIVE certificate.

Available today (OpenAPI)

POST /agent/wallet/nonce
POST /agent/wallet/verify
POST /agent/protection/offer
POST /agent/protection/purchase
GET /agent/protection/certificates/{id}/payment-intent
POST /agent/protection/certificates/{id}/confirm-payment
GET /agent/protection/certificates/{id}
npm: @sima-prime/agent-sdk
MCP: npx @sima-prime/mcp-server (read-only discovery)

SIMA V1 economics

Premium = 5% of protected amount
Coverage = 50% of protected amount
Deductible = 10% of protected amount
Maximum net payment = 40% of protected amount
Denomination = protected contract asset

Offer example

Asset-denominated commercial terms.

Response shape from POST /agent/protection/offer. No USD commercial fields.

{
  "contractVersion": "SIMA_AGENT_PROTECTION_OFFER_V1",
  "protectedAmount": "1000",
  "premiumAmount": "50",
  "coverageAmount": "500",
  "deductibleAmount": "100",
  "maximumNetPayment": "400",
  "rulesVersion": "SIMA_V1_50_5_10_40",
  "purchaseEndpoint": "POST /agent/protection/purchase"
}

Safety boundary

The SDK and public agent API do not store private keys, sign transfers, approve claims, or execute payouts. The caller sends SOL on-chain using payment-intent instructions, then confirms with the transaction signature. Confirm-payment verifies RPC and activates the certificate when valid.