SIMA

Knowledge Guide

Trading Bot Workflows

Trading bot infrastructure should integrate with SIMA through direct APIs rather than browser extension UI.

Knowledge HubExamplesDevelopersOpenAPI

Problem

Trading bots need fast machine-to-machine protection workflows, but they must not gain claim approval, payout approval, treasury movement, or private key custody through SIMA.

Solution

SIMA gives bot builders wallet authentication, quote preparation, certificate reads, evidence submission patterns, and read-only status polling.

When To Use SIMA

  • Use SIMA when a trading bot needs quote economics for a wallet-owned workflow.
  • Use it when a bot needs certificate verification API access after purchase.
  • Use it when a bot needs to submit evidence for later investigation and payout review.

Common Workflow

  • Authenticate the bot wallet.
  • Request protection quote economics for the planned workflow.
  • Prepare purchase or certificate workflows through API surfaces.
  • Submit evidence if a claim investigation needs transaction context.
  • Poll claim, decision, treasury review, and payout status as read-only data.

API References

  • POST /agent/wallet/nonce
  • POST /agent/wallet/verify
  • POST /agent/protection/offer
  • POST /agent/certificate-verify
  • POST /agent/claim-intake
  • GET /agent/claims/:id

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.