/api is intentionally unavailable.
Developer preview
One API boundary.
The API contract is implemented and tested locally. The public production endpoint is not enabled yet, so the examples below are documentation—not a claim of live availability.
A challenge proves address control without moving funds.
Persistent locally; production database pending.
OpenAI-compatible proxy; production provider pending.
Request lifecycle
- Request a short-lived challenge for a wallet address.
- Sign the challenge and exchange it for a session token.
- Send a prompt with the bearer token.
- Aurelia reserves Credits, calls the provider and refunds the reservation if the provider fails.
Planned endpoints
| Method | Path | Purpose |
|---|---|---|
| GET | /api/health | Service and indexer health |
| GET | /api/config | Public chain and contract configuration |
| POST | /api/auth/challenge | Create a wallet login challenge |
| POST | /api/auth/verify | Verify signature and issue session |
| POST | /api/chat | Metered inference |
| POST | /api/quote | Signed AURL-to-Credits quote |
Privacy boundary
Prompt content is designed not to be stored in the Credits database, but it is sent to the selected model provider. Provider-specific retention and training terms must be disclosed for every route before production access opens.
Release gates
Production requires audited contracts, verified addresses, multisig ownership, managed signer storage, database backups, monitoring, reconciliation and published fee and privacy policies.