Developer platform

The same core, through a programmatic door

One endpoint gives you what the interface gives: every mind, every deterministic engine, every depth. Not a reduced edition.

Create a keyA free trial allowance of 100 GTU — once per lifetime.

endpointPOST

/v1/think

{ message, language, attachments?, conversationId?, personaHint? }

What is not partitionedFull capability through the endpoint: every mind, every deterministic engine, every depth. The only difference from the interface is that entry is programmatic and metering is per key.

Why one endpoint and not twenty

Most platforms split their capability across many endpoints, so the developer must learn which one serves which case — and the split itself becomes a surface for error.

GAIBRA has one: POST /v1/think. You send text, a language, and attachments if any, and the request travels the same pipeline the interface travels — the same routing, the same engines, the same rendering.

Capability is not partitioned: there is no "basic" API plan that withholds the deeper minds. The only difference is that entry is programmatic and metering lands on the key rather than the user.

The key and what governs it

  • A key is shown in full once, at creation, then stored hashed beyond recovery.
  • Rotation issues a new key with a grace period for the old one — no interruption.
  • Scopes are limited per key, on the principle of least privilege.
  • Metering is per key, so you know which integration consumes what.

Billing

Prepaid credit by default. Approved enterprise customers may be invoiced in arrears under contract.

The weight charged is the same work weight applied in the interface — there is no second table for the API.

Credit and its bands

Prepaid credit: you top up an amount and receive units at the rate of the band you land in. The larger the top-up, the cheaper the unit.

Band Top-up amount (USD) Price per GTU (USD)
Entry25 — 99.990.25
Anchor100 — 499.990.20
Commit500 — 1,999.990.17
Scale2000 and above0.15

Minimum top-up: 25 · Credit does not expire with time

Limits and guards

Request limits are declared in advance rather than discovered at rejection time.

request limits

Request limits

  • Max message length: 64,000 characters
  • Max attachments per message: 20
  • Max attachment size: 50 MB
  • Max total injection: 170,000 characters

single request cap

The single-request guard

Every request is bounded by a cost ceiling of 0.50 USD and 12 calls. A request that exceeds it is stopped at the gate and is not billed to you. The API does not exempt itself.

What this page does not give youThe full endpoint reference and code samples are not here — they live in the keys panel inside the platform, where the key, the credit and the metering sit together. This page describes the model; it does not document it.