The Platform API is RenLayer’s control plane. It is a multi-tenant REST API written in Rust + Axum and backed by PostgreSQL. The console is its primary client; you can also use it directly to integrate RenLayer with your own tooling, dashboards, or workflows.
What the API exposes
- Tenants: billing and configuration units, top of the multi-tenant tree.
- Users and roles: operator identity and authorization for the console.
- Agents: the registered AI agents that traffic flows through.
- API keys: agent-scoped credentials.
- Policies: the rules the proxy enforces.
- DLP detectors and patterns: the data-loss prevention configuration.
- Traces and sessions: every action the proxy has recorded.
- Audit log: every operator action in the console.
If a resource is visible in the console, it is reachable through the API.
Design
- REST: JSON over HTTPS, predictable resource URLs (
/tenants/:id/agents/:id). - Versioning: URL-prefixed (
/v1/...); breaking changes increment the version. - Pagination: cursor-based for list endpoints; cursor is opaque.
- Filtering: query parameters; consistent across resources.
- Errors: RFC 7807 problem-detail JSON with stable error codes.
- Idempotency: write endpoints accept
Idempotency-Keyheaders.
Authentication
All requests require a JWT in the Authorization: Bearer … header. JWTs are issued by the OTP login flow or by SAML/OIDC depending on tenant configuration. See authentication for the issuance flow.
Multi-tenancy
Every endpoint scopes its data to the calling user’s tenant. There is no admin endpoint that can read across tenants from the standard JWT, cross-tenant access requires a separate, audited mechanism reserved for support engagements.
What is in this section
The API reference is gated. The pages in this section cover:
- Authentication: how to obtain and refresh a JWT.
- API concepts: the resource model at a high level.
- Request access: request the full endpoint reference.
The full endpoint reference (paths, parameters, schemas, error codes, rate limits) is provided to qualified customers and partners under NDA. This keeps the technical surface predictable for production users while limiting competitive exposure.