SIMA

Machine Access

For bots and AI agents, the API is the product.

SIMA supports direct machine-to-machine access for autonomous systems. Browser extensions are optional for humans and are not required for agents. Bots can use SIMA APIs directly for wallet auth, quotes, payment preparation, certificate workflows, evidence-aware claim status, and claim intake/status without UI interaction.

Demo FlowExamplesBot ManifestOpenAPIDevelopers

AI agents

Use wallet-first SIMA APIs directly. No browser extension or human UI is required for machine-to-machine integration.

Trading bots

Use wallet-first SIMA APIs directly. No browser extension or human UI is required for machine-to-machine integration.

Autonomous wallets

Use wallet-first SIMA APIs directly. No browser extension or human UI is required for machine-to-machine integration.

Wallet copilots

Use wallet-first SIMA APIs directly. No browser extension or human UI is required for machine-to-machine integration.

Solana trading systems

Use wallet-first SIMA APIs directly. No browser extension or human UI is required for machine-to-machine integration.

Portfolio bots

Use wallet-first SIMA APIs directly. No browser extension or human UI is required for machine-to-machine integration.

Sniper bots

Use wallet-first SIMA APIs directly. No browser extension or human UI is required for machine-to-machine integration.

Research agents

Use wallet-first SIMA APIs directly. No browser extension or human UI is required for machine-to-machine integration.

API-First Access

Extensions are optional. APIs are direct.

Human users may use browser or portal interfaces, but autonomous systems can integrate with SIMA through the agent API surface: wallet authentication, quote-only economics, treasury destination discovery, payment intent preparation, certificate verification, certificate portfolio retrieval, certificate status visibility, and claim intake/status.

Discovery

Machine-readable discovery files

Bots, agents, and registry systems should start with the structured discovery files before calling the full OpenAPI schema: bot-manifest.json, agent.json, agent-capabilities.json, llms.txt, and openapi.json.

Direct API Capabilities

  • Wallet-based agent authentication
  • Protection quote economics
  • Treasury payment destination discovery
  • Payment intent preparation
  • Payment evidence submission and review
  • Certificate verification
  • Certificate portfolio retrieval
  • Certificate request and finalization status visibility
  • Certificate and coverage status visibility
  • Claim intake preparation
  • Claim status retrieval

Safety Limits

  • No automatic certificate issuance without purchase
  • No automatic claim approval
  • No automatic payout approval
  • FULL_PAYMENT requires treasury review before payout execution
  • Payment review required where applicable
  • No browser extension required for agents

Trust Visibility

Agent Trust & Reputation

SIMA may maintain operational trust profiles for agents and wallets to understand authentication, quote, payment-prep, certificate, and claim-intake behavior over time. This is operational monitoring only: it does not approve claims, deny claims, issue certificates, execute payouts, or expose public reputation scores to agents.

SIMA V1 Economics

Premium
5% of invested amount
Coverage
50% of invested amount
Deductible
10% of invested amount
Maximum Net Payment
40% of invested amount

Claim outcomes are FULL_PAYMENT or NO_PAYMENT only.

The agent API does not approve assets, approve claims, perform payouts, execute blockchain transfers, or automatically issue certificates. FULL_PAYMENT is a decision that still requires treasury review before payout execution.