Two ways to create company memory for paid packages
Metiora packages are not free-form essays. They are generated from founder and startup memory. Marketplace buyers need a way to create that memory without operator keys — and without a mandatory free call before every purchase.
Every paid product needs founder and startup context. That is not cosmetic: generators load memory from those records, and ownership checks stop one buyer from attaching another founder’s company by guessing UUIDs. Production supports two body modes so first-time marketplace buyers and returning sessions both work cleanly.
Mode A · Inline on the paid call (recommended for first purchase)
Send founder and startup objects on the product POST itself. After x402 payment
verifies, Metiora auto-bootstraps profiles and generates the package. Minimum fields are founder
email + fullName and startup name + industry. Recommended fields (problem, product, traction, and so on)
produce stronger personalization. This is the path most OKX marketplace buyers should use.
Mode B · Free bootstrap, then profile IDs
POST /v1/a2mcp/bootstrap creates the minimum founder and startup records and returns two
UUIDs. Later paid calls send founderProfileId and startupProfileId. Bootstrap
does not list every profile, delete data, or unlock free packages. If the email already exists, the
founder is reused and a new startup can still be attached.
The false choice we refused
Early designs only allowed profile creation behind the Metiora API key — safe for an operator, useless for a marketplace buyer. The opposite design, making all memory routes public, invites spam and free generation side doors. Public bootstrap plus paid inline auto-bootstrap is the middle path: buyers can start, operators keep a closed control plane, and package generation still requires payment.
Sparse memory is not a reason to punish a paid buyer
Early profiles are incomplete. Hard rejecting “not investor ready” after a successful payment path feels like the product took the money and shrugged. Metiora prefers soft readiness: deliver the package, mark gaps clearly, and leave the buyer with something usable and a path to enrich memory later.
The product principle
Marketplace UX has to respect both sides of the door. Buyers need a legitimate way to start in one paid request or via free bootstrap. Operators need a closed control plane. Memory exists so payment means delivery grounded in the buyer’s company — not “profile not found.”