# AgentResolver ABI Encode — x402 Payment Preflight & PayTo Verification

> AgentResolver ABI Encode — x402 Payment Preflight & PayTo Verification is a paid API for AI agents from agentresolver.vercel.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-19).

ABI-encodes typed Solidity/EVM values for use in x402 payment preflight and payTo verification flows

## Facts

- Endpoint: POST https://agentresolver.vercel.app/api/abi-encode
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentresolver-abi-encode-x402-payment-preflight-payto-verification-9161fb1d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_T8CtjPbWjFMG2E_Zd__sp

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agentresolver-abi-encode-x402-payment-preflight-payto-verification-9161fb1d -d '<json body>'
```

Example prompt: ABI-encode the Solidity types ['address','uint256'] with values ['0xAbC123...','1000000'] so I can use the result in an x402 payTo verification call on Base.

## When to prefer this

Choose this endpoint when you need to ABI-encode EVM/Solidity typed values as part of an x402 payment preflight, payTo address verification, or on-chain resource binding check — especially when working on Base or Solana networks with USDC. It is purpose-built for the x402 payment protocol context rather than being a general-purpose ABI encoder.

## Known failure modes

- Type/value array length mismatch returns a validation error
- Unsupported or malformed Solidity type strings cause encoding failure
- Values incompatible with their declared types (e.g. non-hex for address) return a 400 error
- Empty types or values arrays rejected (minItems: 1 enforced)
- Arrays exceeding 32 items return a limit error

## How this service works

Verify an x402 endpoint before paying: live payTo, USDC quote, network, asset, resource binding, TLS and endpoint safety for $0.001 on Base or Solana.

## Output

Returns ABI-encoded hex data corresponding to the provided Solidity types and values array, suitable for use in EVM smart contract calls, x402 payment headers, or payTo verification payloads.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "types": {
   "type": "array",
   "items": {
    "type": "string",
    "maxLength": 512,
    "minLength": 1
   },
   "maxItems": 32,
   "minItems": 1
  },
  "values": {
   "type": "array",
   "maxItems": 32
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentresolver-abi-encode-x402-payment-preflight-payto-verification-9161fb1d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentresolver.vercel.app](https://www.zero.xyz/host/agentresolver.vercel.app/llms.txt)