# Beggar Bot Permit Submit (Base Mainnet)

> Beggar Bot Permit Submit (Base Mainnet) is a paid API for AI agents from beggar-bot-demand.beggarbot.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-11-04).

Submits a permit signature for USDC on Base mainnet, enabling gasless token approvals via EIP-2612 permit functionality.

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/permitsubmit?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/beggar-bot-permit-submit-base-mainnet-02755327
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wmRhrpYqLK91ljtQWQZuD

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 beggar-bot-permit-submit-base-mainnet-02755327
```

Example prompt: Submit my signed USDC permit on Base mainnet so the spending is authorized — here are my permit parameters including the owner address, spender, value, deadline, and v/r/s signature components.

## When to prefer this

Use this endpoint when you need to relay a pre-signed EIP-2612 permit for USDC on Base mainnet, enabling gasless token approvals as part of an automated or agent-driven payment workflow. Prefer this over manual on-chain approve transactions when the user has already generated a permit signature off-chain.

## Known failure modes

- Expired permit deadline returns error indicating signature is no longer valid
- Invalid or malformed v/r/s signature components cause rejection
- Nonce mismatch if permit was already used or resubmitted
- Insufficient payment (0.02 USDC via x402) results in 402 Payment Required response
- Network unavailability on Base mainnet causes submission failure
- Wrong USDC contract address or chain ID mismatch causes transaction revert

## How this service works

Paid: /v1/verify, /v1/risk, /v1/receipt cost $0.01 USDC per call on Base mainnet via x402 (payTo 0x719227f384b66BFEF00093D6d8d32fA9dC2B40e7); utilities analyze Base mainnet (USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) by default, network=base-sepolia optional; /v1/receipt/verify and discovery files are free. Operator: Beggar Bot.

## Output

Returns a JSON response indicating whether the permit was successfully submitted on Base mainnet, including any transaction hash, on-chain status, or error details if the permit was invalid, expired, or already used.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/beggar-bot-permit-submit-base-mainnet-02755327/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from beggar-bot-demand.beggarbot.workers.dev](https://www.zero.xyz/host/beggar-bot-demand.beggarbot.workers.dev/llms.txt)