Agentic Portal
Total Control Suite · machine payments only
Buy, provision and operate your own organization.
The Agentic Plan lets an AI agent buy wall-clock timed sessions with a single machine payment, then register and activate the organization. A $1 setup provisions your org + sole admin and opens a 60-minute first session; later access is bought as timed sessions ($0.50/15, $0.65/30, $0.80/45, $0.95/60). You call an endpoint, pay the HTTP 402 challenge, and receive a one-time registration token; you then register your account, read an OTP from your own mailbox, and activate. The first session window starts at activation. Every capability in the Total Control Suite is included.
Payment boundary: enterprise seat-tier packages bill by card via Stripe. The Agentic plan is paid in USDC on Base through the x402 rail; card payments are not accepted for this plan. A Stripe Machine Payments Protocol (MPP) rail is proposed, subject to Stripe approval, and is not currently offered or supported.
Timed sessions · single agent tier
Setup — first purchase
Provisions your org + sole admin, then opens the first 60-minute session (clock starts at activation).
$1.00
one-off
Replenish sessions — extend an existing org
$0.50
session: "15"
$0.65
session: "30"
$0.80
session: "45"
$0.95
session: "60"
Pay per window of wall-clock access. A session extends your access from the later of now or your current window end — run as much as fits, then buy the next window. Your org, admin, saved reports and vault persist across sessions.
Baseline & guardrails
- The agent selects the baseline. On this plan the agent chooses the optimization target (a prompt library, a single prompt, or its own execution traces) and the aspects it optimizes. The platform records what was chosen together with the metrics the agent reports; it does not select the baseline, validate it, or endorse the resulting delta.
- Enterprise guardrails govern the work. The organization that owns the agent sets its instructions, and the agent must optimize within them: approved targets and modules, permitted data, resource and spending limits, escalation and approval requirements, and prohibited actions. It must also stay inside the platform's enforced limits — entitlements, seat and administrator limits, row-level security, and rate limits.
- Reproducible, not certified. Every iteration is deterministic and re-runnable, so a reported delta can be recomputed and checked. Reproducibility does not prove the baseline was the right one, that an improvement is real, attributable, or durable, or that any enterprise policy or standard was met. Review and approval remain with the organization.
- Agent-supplied figures. Optimization metrics are supplied by the agent and are not independently verified by the operator. The agent, and its organization, remain responsible for its inputs, its baseline, its decisions, and any action taken in reliance on the output.
Zero-knowledge & security
- No external API calls. All analysis runs client-side; prompts never leave your browser.
- Buyer email is one-way SHA-256 hashed before storage; the registration token is stored as a hash and cleared after activation.
- Anti-tamper and anti-scraping protections stay fully active even in sanctioned headless-agent sessions — your automated workflows are protected exactly like a human's.
Deterministic machine API
- A copy-paste HTTP endpoint for the live USDC-on-Base (x402) rail, typed JSON fields, and a fixed pay → register → activate → login sequence. A Stripe MPP rail is proposed and not currently offered.
- No checkout page — you pay, provision, activate and log in through typed HTTP calls.
- Every response is a stable JSON schema you can code against; provisioning is idempotent on the buyer email hash, so a retry never creates a duplicate org — and a retry only reissues the registration token when it re-presents the payment credential.
Every capability included — Total Control Suite
Machine-readable specification
How to begin
Send an HTTP POST with a JSON body to the x402 endpoint below. The server responds with a 402 payment challenge; sign the permit, then retry the same POST with the payment credential to receive your provisioning receipt. The Stripe MPP rail shown underneath is proposed and not currently offered.
Proposed rail, subject to Stripe approval. It is not currently offered or supported, and no availability, price, or settlement commitment attaches to it. Use the USDC-on-Base (x402) rail to purchase a session; see Legal Disclaimers §10.
Request fields
First access window: "setup" ($1 · 60-min first session + org provisioning), or "15" / "30" / "45" / "60" (that session length as the first window).
Display name for the new organization.
Business email. SHA-256 hashed server-side; the founder uses it to claim the org.
Provisioning sequence
- 1POST JSON to the endpoint with session, org_name and buyer_email (business email required).
- 2Server validates inputs, checks the friendly-fraud blocklist, and returns HTTP 402 Payment Required with an MPP payment challenge for the session price.
- 3Pay the challenge amount via your MPP wallet (Shared Payment Token or stablecoin).
- 4Retry the same POST with the payment credential → 200 OK receipt: { org_id, registration_token, register_url, already_provisioned }. Idempotent on the buyer email hash — a retry of a fulfilled challenge never creates a duplicate org. The retry must re-present the payment credential, which rotates the registration_token (valid 24 hours, single-use).
- 5Call registerAgenticOrg (register_url) with the registration_token to register and activate your account — the first session window (minutes) starts at activation. See Self-registration below.
Request fields
First access window: "setup" ($1 · 60-min first session + org provisioning), or "15" / "30" / "45" / "60" (that session length as the first window).
Display name for the new organization.
Business email. SHA-256 hashed server-side; the founder uses it to claim the org.
Provisioning sequence
- 1POST JSON to the endpoint with session, org_name and buyer_email (business email required).
- 2Server returns HTTP 402 with a base64 PAYMENT-REQUIRED header (x402 v2 challenge); the amount is the session price in USDC on Base.
- 3Sign an EIP-3009 / Permit2 permit for the session price in USDC on Base (mainnet eip155:8453; Base Sepolia eip155:84532 fallback).
- 4Retry the same POST with the payment-signature header (base64 PaymentPayload) → the CDP facilitator settles onchain → 200 OK receipt: { org_id, registration_token, register_url, already_provisioned }. The registration_token is short-lived (24 hours) and single-use, and is only issued against a verified payment.
- 5Call registerAgenticOrg (register_url) with the registration_token to register and activate your account — the first session window (minutes) starts at activation. See Self-registration below.
Request fields
One-time token issued in the payment receipt. Short-lived (24 hours) and single-use — burned at activation. SHA-256 hashed server-side; never persisted raw.
Organization id from the payment receipt. Optional — resolved from the buyer email if omitted.
The buyer email used at payment. Must match. One-way hashed server-side; never persisted raw.
New account password (min 8 chars). The agent uses email + password to log in at /login afterward.
Omit on the first call to create the account (OTP emailed to the agent's own mailbox). Include on the second call to verify and activate.
Activation sequence
- 1Phase 1 — call registerAgenticOrg with registration_token, email and password (no otp_code). Server validates the token, creates your (unverified) account, and emails a 6-digit OTP to your own mailbox. Returns 200 { phase: 'otp_sent', org_id }. On a retry where the account already exists, the OTP is resent.
- 2Read the 6-digit OTP from your own email mailbox.
- 3Phase 2 — re-call registerAgenticOrg with the same fields plus otp_code. Server verifies the OTP, activates the org (you become sole founder/admin, subscription_status → active), stamps the first session window (agentic_period_end = now + purchased minutes; the clock starts at activation), and clears the single-use token and email hash. Returns 200 { activated: true, org_id, user_id, access_token }.
- 4Log in at /login with email + password through your own headless browser. member_id is minted automatically on first authenticated app load. A replay against an already-active org returns 200 { already_activated: true, org_id } without re-verifying.
After activation, mint a headless session token and drive the real UI. No request body — authenticated by your active Agentic session.
Response fields
true on success.
HMAC-signed headless session token (base64url.payload.sig).
When the token expires.
Token lifetime (3600 = 1 hour). Re-mint before expiry to renew.
Stands down
- AntiTamper devtools block
- Turnstile human puzzle
Stays enforced
- Authentication
- Row-level security (RLS)
- Rate limits
Sequence
- 1Pay and activate via /functions/payAgenticTier (or /functions/payAgenticTierX402) then /functions/registerAgenticOrg.
- 2Log in at /login with email + password through your headless browser (the activation OTP is read from your own mailbox during registration).
- 3POST /functions/mintHeadlessSessionToken with no body, using the authenticated session. Requires an active Agentic-plan org. Returns { ok, token, expires_at, ttl_seconds }.
- 4Store the token in localStorage under __ft_headless_session and dispatch a window "headless-session-change" CustomEvent so AntiTamper + Turnstile detect it.
- 5Drive the real UI (routes below). AntiTamper's devtools block and the Turnstile human puzzle stand down for the session; auth, RLS and rate limits stay fully enforced.
- 6Re-mint before the 1-hour TTL to renew — call the same endpoint again and overwrite the stored token.
Drivable routes