Skip to main content
Social orders use /{network}/{service}, where network is solana or base. Send the intended target and quantities, inspect the returned x402 quote, and pay with PAYMENT-SIGNATURE. Creation does not require an API key or account login.

​
Public services

The unified vote endpoint accepts voteType:"coingecko_vote" or "coinmarketcap_vote", url and amount. Consult advertised x402 OpenAPI for service-specific schemas and aliases.

​
Counts and instructions

Many single-action routes accept amount; bounds and defaults differ by service. For example, X likes accepts 5–250, default 40; X views accepts 10–5000, default 100; X verified followers accepts 5–100, default 100. Use explicit integer counts so the request reflects the intended purchase. Instagram and YouTube comments accept optional instructions. Use a canonical public target URL; a missing target can return a discovery descriptor rather than a quote for an actual job. For custom raids, xraid/custom takes url, likes, reposts, comments and bookmarks. The verified variant is xraid/xverified/custom. For verified custom raids, each count is 0 or 5–100, with at least one active component. Inspect the returned package and every component; verified presets gate engagement components while views remain ungated.

​
Quote and pay

Replace the example target before requesting a real quote. Inspect its exact network, asset, recipient, amount and resource before signing. Prices in schemas or examples do not replace the actual payment requirements. A social quote commonly binds a canonical /api/x402/jobs/{jobId}/pay resource, or /api/x402/base/jobs/{jobId}/pay. Use that returned payment resource, or retry the unchanged public request with the saved proof. Preserve all identifiers, the original signed payment and any receipt. See payment and recovery rules. An uncertain response does not authorize another charge. A 409 can mean a similar paid job is already open; inspect the returned details before trying again. Order creation and paid status establish a funded campaign, not completed engagement or guaranteed delivery speed.

​
Recover a social payment

With SDK/CLI 0.7.1, payments resume for social jobs and raids uses only the original local journal and makes no HTTP request. It can restore a complete quote or validated response already saved there. It cannot query remote payment or fulfillment status or retrieve job/raid IDs missing from a lost or truncated response. A result with fulfillment:"not_observed" does not establish delivery. Keep the original state directory, operation and request references, any job/raid IDs, transaction ID and paymentAttemptId. If the outcome remains unresolved, contact support with the available references and attempt time. Keep signed payments and the state directory private. Do not change the request ID, prepare a replacement order or sign another payment to resolve uncertainty.