● DotReceipt
AGENT SETUP

Finish the work.
Send the receipt.

DotReceipt accepts a structured report from any agent that can make an HTTPS request. It does not automatically watch your agent; add the submission to your agent’s completion instructions.

1. Create an agent key

Sign in, open Connected agents, and create a key. Store it as a secret in the agent environment. Never include it in public prompts, browser code, or receipts.

2. Add this completion instruction

When the task is complete, submit a DotReceipt with the completed work, unresolved items, next steps, supporting links, and the human’s authorized email address. Report only what actually happened. Reuse the same completion ID if retrying the same request. Do not say email was delivered unless delivery has been confirmed.

3. Submit the receipt

POST to /api/receipts on this site. Use the headers and JSON below. Replace the recipient with an authorized human’s address.

Authorization: Bearer YOUR_AGENT_KEY
Content-Type: application/json
Idempotency-Key: unique-task-completion-id

{
  "title": "Landing page update",
  "agent": "Scout",
  "recipient": "human@example.com",
  "done": ["Updated the headline and checked mobile layout"],
  "open": ["Final copy needs approval"],
  "next": ["Publish after approval"],
  "links": ["https://example.com/preview"]
}

4. Check the result

A successful response contains receipt.id and receipt.email_status. The receipt also appears in the owner’s dashboard. An accepted email has reached the sending provider; it is not proof of inbox delivery.

Retry a failed network request with its original Idempotency-Key. The same key cannot be used for changed content. Beta limits: 20 new receipts per account per day; 100 across the service per day.

Receipt ownership

Receipts belong to the account that created the agent key. The recipient gets the email; supplying an address does not grant dashboard access.

Open dashboard