Your customers start companies without leaving your product.
One portfolio per customer, one scoped API key — Matter handles formation, filings, and compliance behind your interface.
Formation becomes a feature of the products people already run their work in.
Every example below is the platform's own interface. Matter ships the API underneath, not the UI — each formation step you see is a call their backend makes.
Fintech and banking platforms
Business banking starts with a business. Offer formation inside onboarding so a customer can open the company and the account in one flow.
Formation runs during onboarding — the entity.state_changed webhook opens the account.
AI app builders and dev tools
Your users build products that need a company behind them. A button — or an agent — in your builder can form a real entity through one API call.
One tool call from the agent — POST /v1/entities, scoped to that user's portfolio.
Monetization and creator commerce
Merchant-of-record platforms watch creators cross the income thresholds where an LLC or S-Corp becomes tax-urgent. Offer formation at exactly that moment — high-intent, perfectly timed.
A revenue webhook crosses the threshold — one call forms the entity, payouts re-route to it.
Four calls. A formed company.
Four calls take a customer from sign-up in your product to a formed company with its own event stream. The scoped-token cookbook walks the same flow end to end.
Create a portfolio per customer
A portfolio is the tenancy boundary for one of your customers. The metadata.customer_id field correlates it to your own records.
Mint a key scoped to that portfolio
The key acts only inside that customer's portfolio. It cannot mint other keys, touch webhooks, or see any other customer. Token creation also takes acknowledgements — the cookbook walks through the full request.
Form companies inside the portfolio
Single calls for one company, or a batch of up to 25 with per-item results. Formation, registered agent, and EIN application ride along in the same request.
Route events per customer
Bind a webhook endpoint to a portfolio and it receives only that customer's events. Every event payload carries portfolio_id either way.
Built for fleets of customer companies.
Fails closed by design
A portfolio-scoped key cannot reach outside its portfolio. Cross-portfolio requests return the same 404 as a nonexistent id — indistinguishable by construction.
Up to 25 entities per call
Form a customer cohort in one request. Per-item results, partial success allowed, every outcome reported.
One rollup per customer
A single call returns every obligation across a customer's entities, with the critical actions due first.
Events routed per customer
One endpoint per portfolio demuxes the firehose. No fan-out logic on your side.
File everything due at once
One workflow call sweeps a portfolio and files every due obligation across its entities.
Audit trail and export
Read the audit chain scoped to a portfolio, and pull an export manifest of everything Matter holds when a customer offboards.
Questions platforms ask.
How do I keep my customers' data isolated?
Each customer gets a portfolio, and you mint an API key scoped to that portfolio. A portfolio-scoped key cannot read or write outside its portfolio — a request for another customer's resource returns the same 404 as a nonexistent id. Your own org key keeps full visibility for support and operations.
Can my customers form a company without leaving my product?
Yes. Your interface stays in front of the user while your backend calls the Matter API — there is no Matter front end inside your product. When you do want a hosted step, formation sessions are Matter-hosted pages that carry your own brand: your logo, your accent color, your product name.
How do I get events for one customer at a time?
Create a webhook endpoint with a portfolio_id and it receives only that portfolio's events. Every event payload carries portfolio_id, so an org-wide endpoint can route by customer too.
Is there a test mode?
Yes. sk_test_ keys simulate the full lifecycle — formation, filings, documents — with no real government filings, so you can build and demo the integration end to end before going live.
How does pricing work for platforms?
Matter is priced per entity — see the pricing page for the standard rate. For platform volume, contact us and we'll work through your shape.
The whole lifecycle, embedded.
Form each customer's entity inside their portfolio — single calls or batches, with EIN application and registered agent in the same request.
Compliance rollups, filing sweeps, documents, and cap tables — every ongoing operation is an API call scoped to the customer.
When a customer winds down or moves on, dissolve entities through the same API and pull an export manifest of their records.
Start embedding
The platform guide covers the same flow in depth — tenancy, scoped tokens, batch formation, and webhook routing, with runnable requests.