# WarpPay402 Deploy Contract

> WarpPay402 Deploy Contract is a paid API for AI agents from api.warppay402.com, paid per call via x402, $5/call, status unknown (last checked 2026-10-02).

Deploys a non-custodial smart contract (escrow, bounty, subscription, or Pendle) on-chain via the x402 monetization protocol for AI agents.

## Facts

- Endpoint: POST https://api.warppay402.com/api/v1/tools/deploy-contract?utm_source=zero.xyz
- Price: $5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/warppay402-deploy-contract-4969ebcf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_efSspCuHy5jcWfLotGz7l

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 warppay402-deploy-contract-4969ebcf -d '<json body>'
```

Example prompt: Deploy an escrow smart contract for me using WarpPay402 so I can hold funds non-custodially for an upcoming transaction.

## When to prefer this

Choose this endpoint when you need to programmatically deploy a non-custodial smart contract (escrow, bounty, subscription, or Pendle) on-chain as part of an AI agent workflow, especially when using the x402 payment protocol. Prefer this over manual contract deployment when you need automated, agent-driven contract creation tied to MCP tooling.

## Known failure modes

- Missing required 'contractType' field returns a validation error
- Invalid contractType enum value returns a 400 bad request
- Payment not included or insufficient USDC returns a 402 Payment Required
- On-chain deployment failure returns a transaction error with no hash
- Network congestion may cause delayed or failed transaction confirmation

## How this service works

Non-Custodial x402 Monetization Server & MCP Tools for AI Agents.

## Output

Returns a JSON object with a success boolean, the contractType that was deployed, and a transactionHash identifying the on-chain deployment transaction.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "contractType"
 ],
 "properties": {
  "contractType": {
   "enum": [
    "escrow",
    "bounty",
    "subscription",
    "pendle"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "success": true,
  "contractType": "escrow",
  "transactionHash": "0xabc..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/warppay402-deploy-contract-4969ebcf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.warppay402.com](https://www.zero.xyz/host/api.warppay402.com/llms.txt)