SIMA

Knowledge Guide

Agent Authentication

AI agent authentication in SIMA is wallet-first, so agents and bots can use machine-to-machine API access without a browser extension.

Knowledge HubExamplesDevelopersOpenAPI

Problem

Autonomous systems cannot rely on manual browser UI, but they still need accountable identity for protection, evidence, and claim workflows.

Solution

SIMA treats agent identity as wallet identity. Agent developers use the same nonce and verify flow, then call protected APIs using the authenticated wallet account.

When To Use SIMA

  • Use SIMA when an AI assistant, agent runtime, or automation service needs wallet-scoped access.
  • Use it when a trading bot needs an auditable wallet identity before requesting quote economics.
  • Use it when agent actions should remain separate from claim approval or payout authority.

Common Workflow

  • Identify the wallet controlled by the agent or operator.
  • Authenticate through wallet nonce and verification endpoints.
  • Request quotes, certificate records, evidence intake, or claim status through authenticated APIs.
  • Poll read-only status fields without approving claims or executing payouts.

API References

  • POST /agent/wallet/nonce
  • POST /agent/wallet/verify
  • POST /agent/protection/offer
  • POST /agent/claim-intake
  • 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.