ByteBeacon

Forms, live in one prompt!

ByteBeacon is a form backend: point any agent to it, and it will collect form data from users, store it in a database browsable in a dashboard, and exportable as CSV.

the entire signup flow 
$ curl -s -X POST \    $BASE/v1/accounts \    -d '{"email":"[email protected]"}' {  "success": true,  "data": {    "user_id": "usr_…",    "organization_id": "org_…",    "project_id": "prj_…",    "form_id": "form_…",    "secret_key": "bb_sk_…"  }} $
  • UnlimitedSubmissions, on every tier
  • 1 POSTFrom nothing to a live endpoint
  • CSVExport everything, any time
  • llms.txtDocs your agent reads first

Paste a form. That’s the integration.

The form_id is public: it can only send you submissions. Your secret key never touches your site.

Waitlist, contact form, signup sheet: any fields you add are stored as-is. Redirects, JSON responses, and the full snippet are in the quickstart.

paste into any page 
<form method="POST"
  action="$BASE/s/YOUR_FORM_ID">
  <input type="email" name="email" required>
  <input type="checkbox" name="botcheck"
    style="display:none">
  <button type="submit">Join the waitlist</button>
</form>

Unlimited
submissions.
Every tier. Free.

The meter is email delivery, never usage. Storage, the dashboard, and CSV export are free, so a waitlist that goes viral costs you nothing. Paid tiers exist for what email costs us, and for teams that need more control over their data.

$0per submission, per month, forever

free

$0, forever

  • Unlimited submissions
  • Dashboard & CSV export
  • Full API, agent-readable docs
  • No deletion (export anytime)

pro

priced when email ships

  • Everything in free
  • Delete forms & submissions
  • Email support
  • Deeper integrations as they land

Boring where it counts.

Your submissions are someone’s signup. The parts that keep them safe are deliberately unexciting.

  • One response envelope everywhere. Error codes are stable API surface: branch on code, not prose.
  • Secret keys are stored as SHA-256 hashes. The plaintext exists once: in the 201 that created it.
  • Postgres underneath, keyset pagination, streaming CSV export, 64 KiB payload cap, per-form rate limits.
  • Spam handled by a honeypot field in the snippet, so your visitors never solve a captcha.
  • Cross-tenant reads don’t 403. They 404.
every error, same shape
{
  "success": false,
  "error": {
    "code": "rate_limited",
    "message": "…"
  }
}
the whole surface
POST  /v1/accounts
POST  /s/{form_id}
GET   /v1/me
GET   /v1/forms
POST  /v1/forms
GET   /v1/submissions?form_id=…
GET   /v1/forms/{id}/export.csv

Or hand the whole thing to your agent.

Every page you just read has a machine-readable twin: markdown docs, llms.txt, OpenAPI, stable error codes. An agent can discover ByteBeacon, create the account, and wire the form without you opening a terminal.

/llms.txt /docs/quickstart.md /docs/api.md /openapi.json
paste into your agent 
Add a waitlist form to my site using ByteBeacon.
Start at $BASE/llms.txt and follow the quickstart.
Keep the secret key out of the page.