Coding agents ship websites in an afternoon — then stall for two weeks
waiting on logos, copy, and credentials.
BriefGate lets your agent declare what it needs,
sends a branded portal to the client, and chases them until everything arrives.
The agent calls get_intake_results() and keeps building.
The agent does the declaring. BriefGate does the chasing. You get typed data back.
Claude Code calls define_intake() with a typed list of items: logo, copy, credentials, structured data.
An email lands in the client's inbox with a magic link — no password, no account. A branded portal guides them through each item with in-place validation.
BriefGate reminds the client on whatever cadence you pick — the default 2, 5 and 9 days, every hour, or every morning at 7. Quiet hours apply unless you say otherwise, and every reminder lists only what is still missing. The "bad guy" is the robot, not you.
Webhook fires on intake.completed. Agent calls get_intake_results() and gets typed data, signed file URLs, and decrypted credentials — ready to use.
# Agent defines what it needs define_intake({ project_name: "John Finance", client: { email: "[email protected]" }, items: [ { key: "logo", type: "image", constraints: { min_width: 512 } }, { key: "wp_admin", type: "secret" }, { key: "opening_hours", type: "structured", schema: { properties: { mon_fri: {type:"string"} } } } ] }) # → intake created, client emailed { intake_id: "in_8f3k", portal_url: "https://p.briefgate.dev/8f3k", status: "sent" } # Later: webhook fires → agent retrieves get_intake_results("in_8f3k") # → logo url, typed opening hours, # one-time secret token ✓
BriefGate ships as an MCP server. Claude Code calls define_intake the same way it reads a file or calls an API. The full conversation context stays intact — no tab switching, no email threads to summarize later.
Every MCP tool maps to a REST endpoint too, so CI pipelines, other agents, and custom scripts all work without MCP.
Content Snare built a great human-first tool. We built the agent-first counterpart — typed schemas, secrets vault, revision flows, and webhooks as first-class features.
Text, longtext, image, file, file_list, color_list, select, boolean, url, structured (JSON Schema), and secret. The agent gets data it can use directly — not raw strings to parse from a PDF export.
Client's WordPress admin, Stripe keys, API tokens — encrypted end-to-end with libsodium sealed box before they hit the database. One-time reveal via get_intake_results(). Never logged.
Default schedule: T+2d, T+5d, T+9d, then weekly — or any cadence you set, from five minutes up, including a fixed time of day. Quiet hours (8–19 local time). The reminder robot never mentions you — it's "Radim needs a few more items," not "I've emailed you three times."
Register item.submitted and intake.completed webhooks. When a logo is blurry, call request_revision() with a note — client is notified, resubmits, webhook fires again.
Agents can read the tier limits themselves: GET /pricing.json (no auth). No scraping the landing page. The API enforces the same numbers, so there's no drift.
On Solo and Agency, the client sees your logo, your colors, your sender name. They never see "BriefGate." Magic link, no registration, mobile-first, in CZ/SK/PL/DE/ES/EN.
Free tier handles one real project — enough to see the value before you pay anything.
Annual billing saves 20%. Add-ons: SMS credits $5/50 messages · extra 50 GB $5/mo · extra Agency seat $15/mo
POST /v1/intakes from any language, CI pipeline, or agent framework. Cursor, Codex, and custom agent loops all work over REST without the MCP server.get_intake_results() and calls GET /v1/secrets/:token to decrypt — after which the token is invalidated. Secrets auto-expire after 30 days. Available on Solo and Agency.Idempotency-Key header (or the idempotency_key metadata field in MCP). BriefGate deduplicates on that key — a retry returns the original response without creating a second intake or sending a second email. Rate limits also protect against runaway agent loops.The hosted API is not open for sign-ups yet. Leave your email and you will hear from me the day it is, with the first accounts going to people on this list. The MCP package is on npm today if you want to read the tool surface first.
One email when it opens. Nothing else, and no sharing with anyone.