Skip to main content
Murmo offers regulated and risk-bearing products. Access to some of them depends on where you are and on your account’s eligibility.
You are responsible for complying with the laws and regulations of your jurisdiction. Do not use the API to access products that are not available to you where you are.

​
What’s restricted

​
Which endpoints enforce it

Geo restrictions apply to specific write endpoints. Reads are never gated. Enforced (return 403 in a restricted region):
  • Perps — POST /perps/proposals (open), POST /perps/proposals/{id}/increase (join), POST /perps/positions/{assignmentId}/reduce, and POST /perps/proposals/{id}/close.
  • Predictions — POST /predictions/proposals (create) and POST /predictions/proposals/{id}/predict.
Not enforced: all GET reads; the perps claim endpoint; and prediction sell, close, and claim — so a restricted user can still settle and exit a prediction position. Perps uses a narrower restriction list (the US plus comprehensively OFAC-sanctioned jurisdictions); predictions uses a broader list.

​
Identity verification (KYC)

No product currently requires identity verification to trade over the API. If a product adds a verification requirement in the future, it will be completed in the Murmo app (there is no API route for it) and documented here.

​
Funding out is in-app only

Withdrawing funds out of your wallet always requires an interactive in-app session and is never exposed over the API. An API key can deploy your funds into positions but cannot send them to an external address. See Authentication.
Eligibility rules are enforced at the account and product level and may change. If a previously working product starts returning 403, check that your account still meets its requirements in the app.