Integration · Logging
Kyvvu for REST API
Register agents and send their traces to the platform over HTTP, from anything that can make a request.
Set up
A few lines, then every step is checked.
- Register, then log
- POST /api/v1/agents registers the agent; POST /api/v1/logs/batch sends a task's steps.
- Safe to resend
- An Idempotency-Key makes retries safe. Up to 1,000 steps per batch.
- Logging only
- This path records what happened. To block steps before they run, pair it with the local engine.
curl -s -X POST https://platform.kyvvu.com/api/v1/agents \ -H "Authorization: Bearer $KV_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "agent_key": "support-agent", "name": "Support agent", "purpose": "Answers customer support questions from the FAQ and the CRM", "declared_tools": ["read_faq", "read_crm"], "risk_classification": "minimal", "environment": "development" }'Batch rules
What the platform accepts.
A batch that breaks one of these is refused as a whole, and none of its steps is stored.
| Rule | What to send | ||
|---|---|---|---|
| Timestamps | On every step, as RFC 3339 with an explicit offset or Z. It's when the agent emitted the step, even if the batch goes later. | ||
| action_id | On every step.*, unique within the task. Task boundaries may leave it out. | ||
| Batch size | Up to 1,000 steps. A task may be sent in several batches. | ||
| Resending | An Idempotency-Key makes a resend safe. Reusing a key for a different batch gets a 409. | ||
| Wire version | X-Kyvvu-Wire-Version: 1, or nothing. | ||
| Client name | Optional: X-Kyvvu-Client: <name>/<version>, and the Agents page shows your integration by that name. |
Good to know
- Authenticate with an agent API key from the dashboard.
Next
Try it before you install it.
In your browser
The playground
Build an agent's path, pick a policy and watch the engine decide.
On your machine
Five minutes, no account
kyvvu try runs a demo agent against the bundled baseline.