API

Authentication

Bearer tokens over HTTPS. No token carries a signing scope, because there is no signing path to scope.

terminal

curl https://api.accuren.xyz/v1/positions \
  -H "Authorization: Bearer $ACCUREN_API_KEY"

#Scopes

Scope	Grants
`read:positions`	Balances, multiplier, share equivalence, basis
`read:events`	The full event trail, including income with no transaction
`write:wallets`	Add, label, and remove watched addresses
`write:exports`	Generate exports

There is no write scope for funds

Not restricted, not gated — absent. Accuren holds no keys and submits no transactions, so no key it issues can move anything.

Create and revoke keys per integration, never share one between them.
A key is shown once. Store it in your secret manager, not in the repo.
Rotate by creating the new key, deploying, then revoking the old one — both work during the overlap.

Agents get their own key

Give an agent a read: only key. It has no reason to add wallets, and a narrow key limits what a confused agent can do.