Check supported profiles and releases
Distinguish source support, published packages, hosted availability and dated qualification.
Match the guide, package and hosted profile
A request shape in source, an installable archive, hosted enablement and a completed merchant campaign are different facts. Review the matching release and dated qualification before a funded run.
| Mechanism | Supported shape | Main limits |
|---|---|---|
| Exact x402 | Base, Solana and Algorand offers. | GET and defined POST profiles, not arbitrary forwarding. |
| Native Base MPP charge | Base USDC EIP-3009; explicit offer match. | No Permit2, splits or arbitrary tokens. |
| Native Algorand MPP charge | One supported USDC charge and fee policy. | Separate from sessions and manifest extensions. |
| Base x402 batch session | Fixed funded channel and continuation policy. | Sequential controller; serialized receiver/token scope. |
| Solana MPP push session | Fixed opening and continuation policy. | No pull delegation, automatic top-up or cross-channel batching. |
| Algorand multi-item | 2 to 15 ordered job payments plus sponsor. | Explicit merchant extension and fee quote. |
| Algorand invoice | One invoice payment for 2 to 64 jobs. | Per-job price allocation unknown. |
The earlier two-item Algorand profile remains a separate supported contract. Do not interpret newer group counts as permission to alter an older manifest.
This guide covers completed source development. Confirm published archive versions and hosted profile availability from GitHub Releases and the operator. Do not infer deployment from a green fixture suite or use a similarly named unverified package.
Complete documentation index · Dated controlled qualification · Confirm integration availability.