Checkout, confirm, hand off
The human-facing path ends after payment and provisioning. From there, the page prepares a clean AHOP block for the coding agent.
Agent-First Onboarding
MaaS gives your AI agents persistent memory.
You handle billing. Your agent handles integration.
This site is a reference implementation for agent-friendly SaaS onboarding. Humans complete checkout. The success page hands a structured runtime block to a coding agent.
Read docs, integrate runtime, ship
The agent gets the API key, workspace, service source, guide, and docs bundle in one copyable handoff.
Why this is different
The site is built for both readers.
Human pages stay localized and readable. Agent endpoints stay English, deterministic, and easy to fetch.
Canonical docs for agents
Every critical document is exposed as English Markdown and listed through llms.txt and llms-full.txt.
A handoff protocol, not a generic success page
The success page emits a service-aware onboarding block and a downloadable onboard-{workspace_id}.txt file.
How onboarding works
One path from billing to runtime
The flow is intentionally simple: billing for the human, implementation for the agent.
Create the hosted checkout session
Start from Quick Start, open Stripe, and complete payment.
Success page activates the workspace
MaaS provisions the tenant, billing state, and first API key automatically.
Copy or download the agent block
The success page turns live runtime values into an agent-ready instruction bundle.
Implement anchors, memory, recall, feedback
The coding agent connects your product to /v1 without manual operator steps.
Docs map
Everything the agent needs is linked here.
Human docs are localized. Agent docs are English-only canon.
Hosted onboarding
Billing, success page provisioning, and the first runtime call.
Mental model
Understand atoms, anchors, recall, and the feedback loop before building.
Runtime contract
All onboarding and runtime endpoints with concrete requests and responses.
Integration patterns
Use cases for Character Chat / Enterprise Tutor, editorial memory, and enterprise tutor flows.
Operational details
Current SDK position, release notes, and machine-readable bundles.
Proof
See memory in action, then inspect the benchmark rules.
Demo proves continuity. Benchmarking proves the runtime decisions behind it.
See memory in action
The demo is a proof surface, not the product itself. It exists to show that continuity comes from stored memory.
83.2% from the production engine
Read why we reject fake freshness tricks, post-retrieval resorting, and benchmark theater.