Skip to content

Console

Create API keys, add prepaid credit and watch usage and spend, for every Ostra model.

From sign-in to your first call

Three steps, and the same key works wherever you use Ostra.

  1. Sign in

    Use your TestRelic login. The Console asks for your billing details once, before anything else.

  2. Add credit

    Pay by card, from $5 to $999 a payment, to pay as you go. Growth, Pro and Enterprise plans also include Ostra usage.

  3. Create a key

    Name it, choose full access or read only, and set an expiry and a spend cap. Use it in Studio, the CLI, over MCP or the REST API.

TestRelic Console

Ostra · key ready

Balance

Prepaid creditAdded by card, from $5$25.00

API keys

ci-pipelineFull access · $50 capactive
dashboardRead only · expires in 30 daysactive
One key for every Ostra modelPro · Decision

Everything you need to run Ostra

Keys, credit, limits, usage and your team, in one place.

API keys

A key for each pipeline or teammate. Full access or read only, with an expiry, a spend cap and an IP allowlist. The secret is shown once, and a key can be revoked at any time.

Credit and limits

Add credit by card and turn on auto top-up. Set a monthly spend limit with a webhook alert at the percentage you choose, and a cap on each key.

Playground

Try a model in the browser before you write code. Requests are billed to your balance like any API call.

Usage and logs

See usage by task, channel or key, and export it as CSV. Search request logs and open any request to see what was sent and returned.

MCP servers

See which MCP tools are on and which clients call them. Turn a tool off for the whole account.

Team and audit

Invite teammates as owner, admin, developer, billing or viewer. Key, billing and member changes are recorded in an audit log.

Available everywhere you work

The key you create in the Console works in Studio, the CLI, over MCP and the REST API, with the same balance.

Studio

Pick Ostra as the model and watch the agent work a failing run, step by step.

Open Studio
checkout.spec.ts failed on main · 3 of the last 10 runs
 
✓ Read the run — video, steps, network, console
✓ Memory — [data-test=pay-now] renamed in v2.4.1
● Patch the selector and re-run the spec
 
- await page.click('[data-test=pay-now]')
+ await page.click('[data-test=pay-submit]')
 
Waiting for your approval before anything touches disk.

CLI

The same agent in your terminal and, headless, in your pipeline.

Install the CLI
❯ why did checkout fail on staging last night?
 
⏺ memory.search done
⏺ runs.get_failures done
 
The selector [data-test=pay-now] was renamed to
[data-test=pay-submit] in v2.4.1. Two specs still use the old one.
 
model ostra-pro · shop-e2e

MCP

One server for Cursor, Claude Code, Copilot and Codex. Ostra shows up as tools.

Connect an agent
// .mcp.json — Cursor, Claude Code, Copilot, Codex
{
"mcpServers": {
"ostra": {
"type": "http",
"url": "https://ostra.testrelic.ai/mcp",
"headers": { "Authorization": "Bearer $OSTRA_API_KEY" }
}
}
}

API

REST with streaming. One bearer key for every model and every task.

Read the rates
$ curl https://ostra.testrelic.ai/api/v1/chat/completions \
-H "Authorization: Bearer $OSTRA_API_KEY" \
-d '{"model":"ostra-pro","stream":true,
"messages":[{"role":"user",
"content":"Fix the flaky checkout spec"}]}'
 
data: {"choices":[{"delta":{"content":"The flake comes from"}}]}
data: {"choices":[{"delta":{"content":" a renamed selector"}}]}

Frequently asked questions

The Console is where you create API keys, add prepaid credit and try the models, and where you see usage, logs and spend. It is at console.testrelic.ai.

With your TestRelic login. The first time, the Console asks for your billing details; after that you can add credit and create a key.

No. You can pay as you go from a prepaid balance, with no plan. Growth, Pro and Enterprise also include Ostra usage, which is metered and resets automatically: Pro has 10x Growth's, and Enterprise is unlimited.

By card, from $5 to $999 a payment. You can also turn on auto top-up, which adds credit when the balance runs low.

A request with no balance is refused until you add credit. To limit spend, each key can carry a spend cap, and the account has a monthly spend limit.

Each key has a name and either full access, which can run every model and task over the API and MCP, or read only, which can list the models and the MCP tools but cannot run a model. You can also give a key an expiry, a monthly spend cap and an IP allowlist, and revoke it at any time. The secret is shown once, when you create the key.

No. One key works for every Ostra model and every task, in Studio, the CLI, over MCP and through the REST API, and they all draw on the same balance.

Set a monthly spend limit for the account, with an alert at the percentage you choose, and a spend cap on each key. The alert is sent as a webhook and written to the audit log; it is not an email. A request that would go over a limit is refused.

Yes. The Playground in the Console sends a request from the browser. Playground requests are billed to your balance like API calls.

Usage is grouped by task, channel or key over a date range, and exports as CSV. Logs list each request with its status, channel and task, and you can open one to see the request and the response. Bodies are stored truncated, and logs are kept for up to 30 days, or switched off in settings. Usage and billing still count every call.

Yes. Invite teammates as owner, admin, developer, billing or viewer. Key, billing and member changes are recorded in an audit log.

Yes. The MCP servers page shows which tools are on and which clients call them, and lets you turn a tool off for the whole account.