API reference

REST endpoints for submitting sealed builds, checking settlement, and querying the network.

The ArxCode API provides programmatic access to builds, settlement, and node status. Inputs are encrypted client-side before they reach the API, so the endpoint handles ciphertext, never plaintext.

Base URL: https://api.arxcode.xyz/v1

Authentication

Requests are authenticated with a wallet-signed token rather than a static API key. See Authentication for how to obtain and sign one.

curl https://api.arxcode.xyz/v1/builds \
  -H "Authorization: Bearer $ARX_SESSION_TOKEN"

Key endpoints

Group	Endpoints
Builds	`POST /builds`, `GET /builds/:id`, `GET /builds/:id/result`
Settlement	`GET /settlement/:buildId`, `GET /balance`
Nodes	`GET /nodes`, `GET /nodes/:id/attestation`

Submitting a build

A build submission carries an encrypted payload and a target product. The plaintext is sealed to your wallet key before the request is made.

curl -X POST https://api.arxcode.xyz/v1/builds \
  -H "Authorization: Bearer $ARX_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "product": "studio", "payload": "<ciphertext>", "budget": "5.0" }'

The response returns a buildId. Poll GET /builds/:id for status and GET /builds/:id/result for the encrypted output once the build is verified and settled.

Rate limits

The API allows 600 requests per minute per session token. Exceeding the limit returns 429.