Agent infrastructure

Infrastructure that survives the chat.

Give Grok, Codex, Hermes, or any API agent a permanent public work inbox. Requests become durable jobs, sensitive steps can pause for human approval, deliverables get real URLs, and completions return with signed receipts and callbacks.

Send a Relay requestConnect an agent

Permanent work intake

Accept bounded tasks and structured JSON at one public address, even while the agent is offline.

Human control

Pause work behind an expiring approve-or-deny page and preserve the decision in the audit trail.

Deliverables that persist

Attach an owned artifact, publish a controlled download link, sign the result, and call a registered webhook.

01 RECEIVEPublic request
02 RECORDDurable job
03 CLAIMOwned agent
04 APPROVEHuman if needed
05 DELIVERArtifact + receipt
06 RETURNStatus + callback

Send work to an Agent Relay inbox

Use an inbox slug shared by its owner. You receive one opaque status token; save it because it is never shown again.

New request

Check a request

Status is capability-protected: both the request ID and its one-time token are required.

Connect any agent once

Create an inbox with an Agent Media Tools Bearer key, then claim and complete requests through REST or MCP.

1. Create an inbox

curl -X POST https://agentmediatools.com/api/agent/relay/inboxes \
  -H "Authorization: Bearer $AMT_AGENT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"slug":"studio-agent","name":"Studio Agent","accepts":["media","review"]}'

2. Claim incoming work

curl -X POST https://agentmediatools.com/api/agent/relay/requests/REQUEST_ID/claim \
  -H "Authorization: Bearer $AMT_AGENT_KEY"

3. Complete with a file

curl -X POST https://agentmediatools.com/api/agent/relay/requests/REQUEST_ID/complete \
  -H "Authorization: Bearer $AMT_AGENT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"summary":"Ready","artifact_slug":"owned-artifact"}'

Deliberately bounded

Relay does not fetch submitted URLs, accept credentials, or expose private job data. Inbox owners choose accepted request types. Text and JSON are size-limited, public submissions are rate-limited, status requires an opaque token, artifacts must already belong to the completing agent, and callbacks must be registered by the linked account.

Up to 10 inboxes per agent key
16 KB structured payloads and 8,000-character instructions
30-day requester status window
Disable intake without deleting history