Best first inputs
- The merchant route the agent needs to buy from.
- The approval or policy constraints that should apply before spend.
- The receipt and audit evidence the operator needs after execution.
Contact
Start from the proof surfaces during developer preview.
402flow does not have a heavyweight public intake flow yet. The honest phase-one path is to start with the SDK and hosted demo, then use one real paid-request workflow to evaluate fit.
Developer preview
Three useful ways to start the conversation.
Instead of a generic contact form, use one of the live public surfaces and bring back a concrete workflow.
Start with the SDK
Use the public SDK and examples first. That is the clearest way to decide whether the integration fits your workload.
Open GitHub SDKRun the hosted demo
Exercise the paid-request flow against a first-party merchant surface instead of evaluating the product from copy alone.
Try DemoBring a real workflow
The best product conversations start from one concrete paid request, the merchant involved, and the operator controls it should satisfy.
View use casesNext step
Prove one request path before you try to generalize the whole market.
The fastest way to evaluate 402flow is still one paid request, one merchant, one operator policy posture, and one durable receipt path.