Authenticate
Send an Account-scoped API key; the server resolves scope.
Developers
Build on governed logistics decision infrastructure.
Connect applications and agents to the same product-owned capabilities used across Raindex—without creating a second source of truth or authority model.
Developer surface
Interfaces for applications and agents.
Each interface family reaches registered product capabilities. What a given Account may call is decided at request time, not by what is documented.
API
Programmatic access to supported Raindex capabilities from your applications and services.
API reference →MCP
Connect compatible external agents through the same capability model over Streamable HTTP.
MCP configuration →External agents
Work with exact, Account-scoped context and call product-owned operations rather than inventing results.
Tool schemas →Authentication
API keys are bound to one Account. The server resolves scope; a key cannot select another Account.
Authentication guide →Capabilities
Availability is capability-specific and Account-specific. Authenticated discovery shows what your Account can invoke.
How availability works →Schemas and contracts
Interfaces expose typed, versioned contracts. Transport never redefines product meaning.
Versioning →Core principle
One capability system. Multiple interfaces.
People use the product UI and Agent. Applications use the REST API. External agents use MCP. Governed SQL covers curated reads. Every path enters the same owner capability with the same validation, confirmation and receipt. Transport does not create authority.
01Product UI
People
02Agent
Raindex Agent
03REST API
Applications
04MCP
External agents
05SQL
Governed reads
06Owner
One capability
Request to receipt
A technical path with an accountable result.
The Account boundary and product owner stay the same regardless of interface.
Read
Inspect an available capability and its exact objects.
Review
For material work, request a fresh Preview and confirm it.
Verify
Follow the owner receipt to the resulting state.
Account context
Private requests stay inside an explicit Account boundary.
Caller identity is not ownership. API keys are created in the signed-in Developer Console, shown once, and revoked there. Backend authorization checks the Account and object on every request.
curl https://raindex-backend.onrender.com/v1/auth/whoami \
-H "Authorization: Bearer $RAINDEX_API_KEY"
# The key resolves its Account on the server.
# Objects from another Account behave as not found.Start building
Go from explanation to integration.
Read the guides and references publicly. Manage credentials and see your Account's availability in the Developer Console.
Bring the workflow your application or agent needs.
We’ll map the request to its supported capability, authority boundary, and receipt path.