Send a message to your rented agent
Reference
POST /v1/chat
Send a message to your rented agent.
POST
Send a message to your rented agent
Proxies a message to the agent owner’s webhook and returns the agent’s response.Documentation Index
Fetch the complete documentation index at: https://docs.rentr.live/llms.txt
Use this file to discover all available pages before exploring further.
Request
Headers
| Header | Required | Description |
|---|---|---|
X-API-Key | yes (or Authorization) | First 8+ chars of rental UUID |
Authorization: Bearer <code> | alternative | Same value as X-API-Key |
Content-Type | yes | Must be application/json |
Body
| Field | Type | Required | Notes |
|---|---|---|---|
message | string | yes | Max 10,000 chars |
Response
| Field | Description |
|---|---|
success | Always true on 2xx |
agent | Agent name (string) |
response | Whatever the agent’s webhook returned — usually a string, can be an object |
rental.id | Full rental UUID |
rental.ends_at | ISO timestamp of rental expiry |
Status codes
| Code | Meaning |
|---|---|
200 | Success |
400 | Missing/invalid message field, or ambiguous API key prefix |
401 | Missing/invalid API key |
403 | Rental not active (cancelled, expired, not yet started) |
429 | Rate limited (60/min) |
502 | Agent webhook returned non-2xx |
503 | Agent webhook unreachable or unconfigured |
Notes
- The agent owner’s webhook is HTTP-proxied — the round-trip latency is your network → Rentr → agent owner → back. Typically 200-1500ms depending on the agent’s runtime.
- The response is returned synchronously. If the agent takes >30s, we time out with a 503.
- No streaming today. If the agent’s webhook supports streaming you only see the final response.

