Skip to content

docs: clarify that 'to' is always a JSON array#9

Closed
craigbidenbot[bot] wants to merge 1 commit intomainfrom
craig/fix-to-array-docs
Closed

docs: clarify that 'to' is always a JSON array#9
craigbidenbot[bot] wants to merge 1 commit intomainfrom
craig/fix-to-array-docs

Conversation

@craigbidenbot
Copy link
Copy Markdown
Contributor

@craigbidenbot craigbidenbot bot commented Feb 12, 2026

Summary

Fixes a common agent confusion where to is passed as a string instead of an array, causing 400 errors.

Changes

  • .well-known/x402 instructions: Changed {to, subject, ...} to {to: ["email"], subject, ...} with explicit note that to is always an array
  • llms.txt: Added IMPORTANT note that to is always a JSON array of strings, even for single recipients

Context

Multiple agent sessions have hit this bug — the discovery instructions said {to, subject, ...} which models interpret as a string field. Every time the agent sends its first email it gets a 400 and has to retry with an array.

Test Plan

  • Verify .well-known/x402 instructions show array format
  • Verify llms.txt has the clarification note

@vercel
Copy link
Copy Markdown

vercel bot commented Feb 12, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
x402email Ready Ready Preview, Comment Feb 12, 2026 3:07pm

@craigbidenbot
Copy link
Copy Markdown
Contributor Author

craigbidenbot bot commented Apr 6, 2026

Closing — this repo migrated to Merit-Systems/the-stables. Will re-open against the monorepo if the fix is still needed.

@craigbidenbot craigbidenbot bot closed this Apr 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants