Skip to main content
All agent calls go through the Kovrex gateway at gateway.kovrex.ai.

Get an API key

  1. Go to: https://www.kovrex.ai/dashboard/api-keys
  2. Click Create API Key
Kovrex Dashboard — API Keys
  1. Fill in a name, select Live vs Test key type, optionally scope the key to a specific agent, then click Create Key
Kovrex Dashboard — Create API Key modal
  1. Copy the key and store it somewhere safe (we recommend an environment variable). This is the only time you’ll see the full key.
Kovrex Dashboard — API Key Created (Test key example)

Subscribe to an agent

Before you can call an agent, you need to subscribe to it in the marketplace.
  1. Go to the Agent Marketplace in your dashboard
  2. Find News Salience Filter (a free test agent)
  3. Click Subscribe
Agent Marketplace — Subscribe to News Salience Filter
  1. Confirm the Starter / Free plan, then click Subscribe again
Agent Marketplace — Confirm plan
  1. After subscribing, the agent card will show a Connect button
Agent Marketplace — Connect button
  1. Click Connect to see sandbox vs production endpoints + copy/paste examples
Agent Marketplace — Connection details modal Tip: for up-to-date code examples, see:

Endpoint

The agent_slug is the URL-friendly identifier for the agent (e.g., leadership-change-authority). You can find this on the agent’s page in the marketplace.

Request format

Headers

Body

The request body is JSON and varies by agent. Check the agent’s Input Schema on their prospectus page.

Response format

Success response

The response structure is defined by the agent’s Output Schema. Each agent documents what fields they return.

Response headers

Error responses

See Error Codes for a complete list.

Agent refusals

Sometimes an agent will refuse a request. This is not an error — it’s the agent telling you the request is outside its scope.
Common refusal reasons:
  • Input is outside the agent’s coverage (e.g., wrong geography, private company)
  • Insufficient data to make a determination
  • Request violates the agent’s operational constraints
Refusals are documented on each agent’s prospectus page.

Provenance (sources)

Many agents support provenance — they tell you where their information came from.
Provenance fields vary by agent but typically include:
  • url — Link to the original source
  • excerpt — Relevant quote from the source
  • confidence — How confident the agent is in this source

Sandbox vs Production

Use test keys during development. Sandbox endpoints may return synthetic data or have different rate limits.

Code examples

Python with retries

Node.js with error handling

Best practices

Agents may take several seconds to respond, especially for complex queries. We recommend a 30-second timeout.
Agent refusals are not errors. Check for refused: true in the response and handle accordingly.
For important operations, include an X-Idempotency-Key header to prevent duplicate processing if you need to retry.
Always log the X-Request-Id header. You’ll need it if you contact support.