create account

Weft field guide

Learn the agentic internet.

Weft uses “agentic internet” as a practical name for the infrastructure that lets software agents discover services, pay under delegated authority, and finish work without a manual handoff.

Start with the category

What is the agentic internet?

Learn Weft’s framework for the shift from human onboarding and static API keys to machine-readable discovery, authorization, payment evidence, and observable outcomes.

Read the primer
  1. IntentThe outcome, its constraints, and a budget — stated as data, not prose.
  2. DiscoverRanked providers for that capability, compared on fit, price and latency.
  3. AuthorizePolicy is checked before any money moves.
  4. PaySettled per call. No account, no API key, no subscription.
  5. ProveA signed receipt, tied to the request that caused it.

Build the mental model

Four focused explainers. Read them in order or enter at the question you have now.

02

Execution

How AI agents buy APIs

A practical guide to the discovery, policy, payment, execution, and receipt loop that lets AI agents buy API access without a manual account handoff.
03

Payments

AI agent payments, explained

How wallets, spending policies, payment challenges, stablecoins, fiat settlement, and receipts work when software agents become buyers.
04

Open protocols

Permissionless protocols for AI agents

How permissionless protocols create an open market where developers can publish services and compatible agents can buy them without marketplace approval.

Know the rails

Protocol guides are reviewed against primary documentation. Each page shows the request flow, trade-offs, and maturity caveats.

X402

x402: HTTP-native payments for agents

x402 is an open payment protocol built around HTTP 402 Payment Required. In x402 V2, a server sends encoded requirements in PAYMENT-REQUIRED, the client constructs a scheme-specific payload and retries with PAYMENT-SIGNATURE, and the server returns the resource with settlement details in PAYMENT-RESPONSE after verification, fulfillment, and settlement.

9 min read MPP

MPP: the Machine Payments Protocol

MPP is an open protocol for machine-to-machine payments co-authored by Tempo and Stripe. Its HTTP flow maps payment into HTTP authentication: the server returns a Payment challenge, the client fulfills a compatible method and retries with a Payment credential, and the server returns the resource after method-specific verification and settlement.

9 min read COMPARE

x402 vs. MPP

x402 and MPP both use HTTP 402 to let machines pay for resources, but their wire formats differ. x402 V2 uses dedicated PAYMENT-* headers and registered scheme/network pairs. MPP maps Challenge, Credential, and Receipt semantics into HTTP authentication, with separate payment-method and intent specifications.

11 min read

Use a real outcome

Install a workflow

Each workflow is a focused skill with an install command, a starter request, and a reviewed example when one exists.

Browse workflows