Skip to main content
FRENT USDC point of sale

Product support

Contact FRENT.

Tell us what you are trying to do and include only public payment or wallet details.

Keep wallet access private. FRENT will never ask for a private key, seed phrase, recovery phrase, wallet password or one-time authentication code.

Your message is encrypted in application storage and used to respond to this request.
Connect Wallet
Menu

Agent payments, with a visible limit.

FRENT AGENT PAYMENTS · x402 v2

Software can discover a price, sign one exact USDC authorization and retry the same HTTP request. No checkout tab and no MetaMask popup are required for a policy-approved agent wallet.

Read the integration OpenAPI reference

One HTTP negotiation

The agent pays; the owner sets the boundary.

  1. 01Discover

    The agent reads FRENT capabilities, OpenAPI or MCP metadata and creates an idempotent payment resource for its merchant.

  2. 02Price

    The resource answers with HTTP 402 and exact Base USDC requirements in the standard PAYMENT-REQUIRED header.

  3. 03Authorize

    The payer signs one expiring EIP-3009 authorization for the exact token, network, amount and recipient—never an unlimited allowance.

  4. 04Settle

    FRENT verifies, settles through the configured facilitator, prevents nonce replay and returns a machine-readable receipt.

Separate product, separate economics

1% per settled x402 payment.

Minimum FRENT fee: $0.002 USDC. Minimum payment: $0.2 USDC. Failed, rejected and expired authorizations carry no FRENT fee. The launch price has no separate facilitator or sponsored-gas surcharge for the merchant.

This is not a discount for bots. Automated payments need facilitator verification, sponsored settlement, replay controls and machine-readable receipts. FRENT POS keeps its existing contract pricing and remains the primary product.

$0.2 payment
$0.002 fee
$1 payment
$0.01 fee
$100 payment
$1 fee
Rounding
Up to the next 0.000001 USDC

Official x402 exact has one recipient. FRENT therefore sends the gross payment directly to the merchant and records the service fee in the merchant fee ledger. Production stays disabled until that accrued-fee collection path is operational.

Authority without custody

An autonomous payment is still a constrained payment.

Exact authorization

The signature fixes chain, USDC contract, amount, recipient, validity window and a random 32-byte nonce.

Replay protection

FRENT binds each verified payer nonce once, while native USDC also rejects an authorization that has already been consumed.

No FRENT payer key

FRENT never receives the payer private key. The agent uses its own wallet, smart-account session or external signing policy.

Spend policy required

Operators should cap per-payment and daily spend, allowlist assets and recipients, and require human approval above a chosen threshold.

Agent API + MCP + x402

Create the payment resource once.

Merchant onboarding remains human-approved: connect the receiving wallet and activate Base on FRENT. After that, an OAuth-authorized agent can create requests and a payer agent can settle them without a browser wallet prompt.

1 · Merchant agent

Create an x402 resource

curl -X POST https://frent.tech/api/agent/v1/x402/payment-requests \
  -H "Authorization: Bearer $FRENT_TOKEN" \
  -H "Idempotency-Key: order-1842" \
  -H "Content-Type: application/json" \
  -d '{"amount":"0.2","reference":"order-1842","network":"base-mainnet"}'
2 · Payer agent

Follow the standard challenge

GET resource_url
← 402 + PAYMENT-REQUIRED

sign exact EIP-3009 authorization

GET resource_url
PAYMENT-SIGNATURE: <base64 payload>
← 200 + PAYMENT-RESPONSE

Initial network scope

Base first. Polygon only when the facilitator proves support.

Base

Implementation target

Native USDC, chain eip155:8453, using the official exact EIP-3009 flow.

Polygon PoS

Conditional

Native USDC supports the authorization primitive, but FRENT only advertises Polygon after the configured facilitator reports eip155:137 support.