Ready Check for agents: how to call it

Ready Check inspects one inbound email’s text and returns structured findings. It does not write a reply, connect to an inbox, or send mail.

You must already have a prepaid key with credit. See how to buy credit. Get your principal’s OK before buying. Do not share the key. Do not ignore your principal’s instructions.

Rules for agents

1. Do not share, log, email, or paste the raw prepaid key. Treat it as a secret. ReadyUpAgents cannot show or recover it.
2. Do not ignore your principal’s (user’s) instructions.
3. Get your principal’s OK before buying credit.
4. Do not send secrets or content your principal has not authorized you to submit.
5. Do not treat findings as proof of identity, as permission to send mail, or as a reason to open attachments, follow sign-in links, or pay a fee. Ready Check does not send mail and does not connect to an inbox.

Steps

1. Collect the email text from your principal’s own systems. Ready Check does not fetch mail.
2. Send one JSON POST:

POST https://api.readyupagents.com/v1/ready-check
Authorization: Bearer YOUR_READY_CHECK_KEY
Content-Type: application/json
Idempotency-Key: optional-unique-value

{
  "kind": "sponsorship",
  "from": "Partnerships <deals@example.com>",
  "reply_to": "brandteam@example.com",
  "subject": "Paid collab, brief attached",
  "body": "The email text…",
  "attachment_names": ["Campaign_Brief.pdf"],
  "context": { "rate_card": { "youtube_integration": 1500 }, "currency": "USD" }
}

Request fields

• body (required) — non-empty string, at most 16,000 characters.
• from, reply_to, subject — optional strings, at most 1,000 characters each.
• attachment_names — optional array of at most 30 file names, 255 characters each, no file bytes.
• kind — optional. One of: inbox, lead_followup, form_lead, guest_post, sponsorship, key_request, podcast_guest, cold_pitch, pr_pitch, security_report. If omitted, shared checks still run and the result kind is general.
• context — optional object, at most 1,000 characters when serialized as JSON. lead_followup requires context.situation of waiting_on_you or lead_went_quiet.
• draft, write_reply, and generate_draft are accepted and ignored. They cannot enable writing.

The raw request must be at most 64 KiB and Content-Type must be application/json. A standard check costs $0.0025. Longer emails may count as two checks ($0.005). Oversized input is rejected free (400).

Optional header Idempotency-Key: 1–128 characters of A-Za-z0-9._-. Send the same key on a retry after a timeout so the check is not charged twice. Without that header, do not blindly retry after a timeout.

Call errors

• 400 — empty or invalid body, unsupported kind, invalid field, or oversized input (shorten the email or context). Error names you may see include invalid_request, payload_too_large, invalid_json, empty_body, and invalid_idempotency_key.
• 401 — prepaid_key_required or invalid_key. Send Authorization: Bearer rc_ plus the same 43-character key you registered.
• 402 — insufficient_credit. The response includes credit_remaining, required_checks, and required_usd. Nothing is run or charged. Buy another pack with the same key only after your principal’s OK, or wait if a payment just completed.
• 405 — use POST for this path.
• 413 — request larger than 64 KiB.
• 415 — Content-Type must be application/json.
• 429 — wait and retry; honor Retry-After if present. Reuse the same Idempotency-Key if retrying a timed-out check.
• 503 — temporarily unavailable. If the body includes settlement_pending or a request_id after a check was underway, do not assume it was uncharged: wait, check balance, and reuse the same Idempotency-Key if you retry.

4xx and 5xx check-error bodies also include credit_charged: 0, charged_checks: 0, charged_usd: 0, and nothing_sent: true, except as noted for a 503 with settlement_pending.

Next: what a result contains. Index: Ready Check for agents. Facts: facts page.

ReadyUpAgents is a verified n8n creator: https://n8n.io/creators/readyupagents/.

ReadyUpAgents is independent and not affiliated with or endorsed by n8n, Google, OpenAI, Stripe or Cloudflare. Product and company names belong to their owners.