BUILD TIMELINE · UPDATED 2026-10-05
Progress for agents.
A public record of what is ready and what is still being prepared. This is about the service build, not customer tasks.
Early pilot · Intake open
Local pilot built
The website, agent guide, OpenAPI schema, request API, private status receipts, validation, rate limits and retention cleanup are implemented and tested locally.
Cloudflare database prepared
A D1 database was created in the operator's Cloudflare account and its initial migration was applied.
Cloudflare DNS delegated
The domain now uses Cloudflare nameservers. Namecheap remains the registrar while the domain is within its transfer lock period.
Contact forwarding configured
Cloudflare Email Routing forwards contact@unblockagents.com to a verified operator inbox. Delivery from a separate sender was tested successfully.
Inbox safeguards deployed
New requests are limited per IP and per UTC day. The Worker notifies the operator with a generated request ID only; submitted text stays in private storage.
Open request intake
The request form and agent API accept limited pilot submissions. Each request is reviewed manually; no fulfillment or response time is guaranteed.
Production flow tested
A marked synthetic agent request reached the database, returned a private receipt, and produced an ID-only email alert. The synthetic database record was removed. This test is not evidence of real agent demand.
Remote MCP pilot interface
A stateless MCP endpoint exposes availability, the approved-offer catalog, manual-review request intake and private status. Daily aggregate operation counts help measure use without storing prompts or client identifiers. No fixed-price agency offers are live.
Agency introductions and business-call guidance
A public agency page now accepts partner introductions for manual review with ID-only email alerts. Business-call guidance states unknown coverage and timing, no price quote, and the need for contact email to receive an answer. These are pilot intake paths, not live provider referrals.
Short human intake and MCP Apps handoff
The human request form now asks for one task description and an optional reply email. Agents retain structured intake. MCP Apps-compatible clients can show an HTML handoff to the form, with a URL fallback; opening it does not submit, book or charge.
Agent inquiry types and scenario trials
Agent API requests can now distinguish a current nonclinical task, an information question and interest in a future nonclinical service. An agent trial cycle tested supported, unavailable and underspecified tasks. Fixed-price checkout and medical callback intake remain unavailable.
Private email previews for review
New operator alerts include a short-lived read-only preview link for manual triage. It does not change agent-facing service availability or create a booking.
For current service availability, read the capabilities endpoint. Agents can read this timeline as JSON.