GET STARTED
Platform overview
Understand models, requests, organizations, and the two ways to observe your agents.
Core concepts
Netra Runtime hosts language models behind an OpenAI-compatible inference API. You send a conversation and receive the model's answer. Your organization's prepaid balance pays for generation. The dashboard provides Playground, usage inspection, API keys, billing, and features available to your organization.
| Term | Meaning |
|---|---|
| Organization | A workspace with its own members, keys, usage, and credit balance. |
| Model | The model ID selected for a request. Use a currently available ID, including an organization model where applicable. |
| Inference | Running a model to generate an answer. |
| Token | A piece of text counted by the model's tokenizer. Tokens are not characters or words; language and content affect the count. |
| Request | One API execution, identified by its request ID. |
| Trace | A related group of operations in an agent run. Each operation is a span; one trace may include several inference requests and tool calls. |
| Agent label | A name your application supplies for attribution. It does not create or host an agent. |
Start from Overview
Overview lists each available model's live input, output, and cache prices. Expand a model card for a request example in cURL, Python, TypeScript, or Go.
Workspace owners and admins can click $NETRA_API_KEY in the example to create a key named Overview quickstart. Copying the request then includes that key. The secret is held only for the current visit and cleared when you switch workspaces; click the masked key text to reveal it and click again to hide it. Manage or revoke the key in API Keys. The created key has no expiration by default and continues to work after you leave Overview. Members should obtain a key from a workspace owner or admin.
Choose your connection
- Generate answers: use
https://api.netraruntime.com/v1as the OpenAI-compatible base URL and call Chat Completions. - Use Anthropic SDKs: configure
https://api.netraruntime.comas the base URL and follow Messages API. - Score text labels: use the Decisions API.
- Send agent observations: export OpenTelemetry traces to
https://api.netraruntime.com/v1/otel/v1/traces. - Investigate observations with an agent: connect the remote MCP endpoint at
https://api.netraruntime.com/mcpusing your workload's API key. - Manage keys and limits with an agent: create a separately permissioned, expiring MCP connection in API Keys and use the same remote endpoint.
Trace export sends observations into Netra. MCP lets your agent read observations already stored in Netra. Neither connection makes an uninstrumented external agent run visible automatically.
These guides are also available at the public documentation page, as a complete Markdown reference, and as compact agent context. For the HTTP schema, see the API reference and OpenAPI document. Model availability, enabled features, limits, and prices can differ by model and organization.