Start / Access
Access is provisioned.
The hosted API is not self-serve. Each instance is single-tenant, and a developer token is issued only after an instance is provisioned. There is no instant key and no public signup.
Hosted
Request an evaluation
For a hosted instance with a provisioned DEVELOPER token. Use the Send an enquiry form on the access page and name the developer API in the brief.
Open the access formPrivate
Deploy inside your perimeter
For a private instance, compiled artifacts, and provenance bound to your deployment. Use the same enquiry form and describe the environment.
Send an enquiryWhat to include
- The intended use and the relation or corpus you want to test.
- Expected request volume and peak concurrency.
- Whether the data can live on a hosted instance or must remain in your perimeter.
- Any compliance, residency, or retention constraint that affects deployment.
- A timeline, if the evaluation is tied to a decision.
What happens next
- 01
Review
The request is reviewed against the intended use and the current instance capacity.
- 02
Provision
An instance is prepared. A hosted evaluation is not a production SLA.
- 03
Issue
A base URL and a DEVELOPER bearer token are issued for that instance.
- 04
Operate
Rotation and revocation are operator actions. There is no self-serve lifecycle route.
Token handling
- Treat the token as a password. Never put it in a URL, commit it, or paste it into a ticket.
- Use TLS. A bearer token has no channel binding.
- If a token is exposed, request rotation. Rotation invalidates the account's older tokens.
- Do not send production secrets or regulated data to an evaluation instance.
Accounts are access control over one substrate. They are not isolated tenants. If two projects must not share memory, they need separate instances.
For the credential model, see Authentication. For the route contract, see HTTP API.