Overview
Every Rilo operation - parameters, notes, and sample requests.
One page per operation, grouped the same way the tools appear to your agent. Each page documents the parameters, behavior notes, and a real sample request for the exact payload that goes over MCP, CLI, and HTTP.
The envelope
Every operation returns the same shape:
{
"ok": true,
"data": {},
"summary": "…",
"signals": [],
"learnings": []
}| Field | What it is |
|---|---|
ok | true on success; failures replace data with error |
data | The operation's payload |
summary | One line saying what happened - safe to show a human |
signals | Anything unusual worth the agent's attention |
learnings | Durable notes the agent may want to keep |
Failures replace data with error: {code, message, hint?, …} and drop
learnings.
HTTP status mapping
| Envelope | HTTP |
|---|---|
ok: true | 200 |
not_found | 404 |
unauthorized | 401 |
forbidden | 403 |
everything else (incl. validation_error, invalid_signature) | 400 |
Unknown extra params are ignored by most operations, but the provider-search
ops (search_people, search_companies, search_companies_hiring,
search_companies_similar) reject unknown params with
validation_error - a typo'd filter must never silently broaden a search.
An unknown operation id returns unknown_operation with
valid_operations[].
Ids are slugs
Envelopes never return raw UUIDs - every id is a human-readable slug
(ceo-leads-x7k2, founder-outreach-x7k2). UUIDs remain accepted on input
everywhere.