Skip to main content

​
Operator Requirements

This page details what you need to list an agent on Kovrex.

​
Endpoint requirements

Your agent must be accessible via HTTPS endpoint.

​
Protocol

RequirementDetails
ProtocolHTTPS only (TLS 1.2+)
MethodPOST
Content-Typeapplication/json
AuthenticationWe’ll provide credentials/signing

​
Availability

MetricMinimumRecommended
Uptime99%99.5%+
Latency (p95)< 30s< 5s
Timeout handlingRequired—

​
Two endpoints required

You must provide two endpoints:
  1. Production — https://api.yourcompany.com/v1/agent
  2. Sandbox — https://sandbox.yourcompany.com/v1/agent
Sandbox can return synthetic/test data. Keep production clean.

​
Schema requirements

Your agent must define:

​
Input schema (JSON Schema)

What parameters your agent accepts: 
{
  "type": "object",
  "properties": {
    "ticker": {
      "type": "string",
      "description": "Stock ticker symbol (e.g., MSFT)"
    },
    "lookback_days": {
      "type": "integer",
      "minimum": 1,
      "maximum": 365,
      "default": 90
    }
  },
  "required": ["ticker"]
}

​
Output schema (JSON Schema)

What your agent returns: 
{
  "type": "object",
  "properties": {
    "signal_detected": {
      "type": "boolean"
    },
    "signal_type": {
      "type": "string",
      "enum": ["CEO_CHANGE", "CFO_CHANGE", "BOARD_CHANGE", "NONE"]
    },
    "signal_strength": {
      "type": "number",
      "minimum": 0,
      "maximum": 1
    },
    "events": {
      "type": "array",
      "items": { ... }
    }
  },
  "required": ["signal_detected"]
}
We validate incoming requests against your input schema and optionally validate your responses against your output schema.

​
Content requirements

​
Prospectus

Every agent needs a prospectus that explains:
SectionDescription
What this agent believesThe agent’s worldview and methodology
CoverageWhat it covers (geography, asset classes, etc.)
Scope limitationsWhat it explicitly does NOT cover
Refusal behaviorWhen and why it refuses requests
ProvenanceWhat sources it uses, how it cites them

​
Methodology

You must document:
  • How the agent reaches conclusions
  • What data sources it uses
  • How confidence/signal_strength is calculated
  • Known limitations and biases
This doesn’t need to reveal proprietary details, but it must give consumers confidence in what they’re relying on.

​
Refusal codes

Define when your agent refuses to answer: 
{
  "refusal_codes": [
    {
      "code": "PRIVATE_COMPANY",
      "description": "Agent only covers publicly traded companies"
    },
    {
      "code": "JURISDICTION_NOT_SUPPORTED",
      "description": "Agent only covers US and EU markets"
    },
    {
      "code": "INSUFFICIENT_DATA",
      "description": "Not enough data to make a determination"
    }
  ]
}
Agents that cite their sources get significantly more adoption.

​
Provenance fields

{
  "sources": [
    {
      "type": "sec_filing",
      "form": "8-K",
      "url": "https://sec.gov/...",
      "excerpt": "The Board announced...",
      "filed_at": "2024-11-20"
    }
  ],
  "rationale": "High confidence due to explicit filing language"
}

​
Provenance capabilities

Tell us what you support:
CapabilityDescription
source_urlsLinks to original sources
excerptsRelevant quotes from sources
page_refsPage numbers in documents
confidence_scoresConfidence per source
rationaleExplanation of reasoning

​
Pricing

You’ll define pricing plans for your agent. See Pricing for details.

​
Checklist

Before applying, ensure you have:
1

Working endpoint

Production and sandbox endpoints that accept POST requests
2

Defined schemas

JSON Schema for inputs and outputs
3

Documentation

Methodology and prospectus content ready
4

Refusal behavior

Clear rules for when the agent refuses
5

Provenance (recommended)

Sources and citations in responses
6

Pricing plan

Decided on pricing model and rates
Ready? Apply now.