# WarpPay402 Deploy Solana Contract

> WarpPay402 Deploy Solana 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 Solana smart contract (SPL escrow, cNFT badge, or Raydium vault) on-chain and returns the transaction signature.

## Facts

- Endpoint: POST https://api.warppay402.com/api/v1/tools/deploy-solana-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-solana-contract-0ea5b5de
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YYWkvE9gGMiuFPuRzmDJp

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-solana-contract-0ea5b5de -d '<json body>'
```

Example prompt: Deploy an SPL escrow contract on Solana using WarpPay402 — use the spl_escrow type with default parameters.

## When to prefer this

Choose this endpoint when an AI agent needs to programmatically deploy a Solana smart contract of a specific type (SPL escrow, cNFT badge, or Raydium vault) without managing custody. It is particularly suited for x402-native agentic workflows where payment is handled automatically per call at $5 USDC.

## Known failure modes

- Invalid contractType enum value returns a 400 validation error
- Insufficient USDC payment causes a 402 Payment Required response
- Solana network congestion or RPC failure may cause transaction timeout
- Malformed params object may result in contract deployment failure
- Transaction confirmation failure if Solana slot is skipped

## How this service works

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

## Output

Returns a JSON object containing a success boolean, the on-chain transaction signature (e.g. '5xyz...'), and the contractType that was deployed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "contractType"
 ],
 "properties": {
  "params": {
   "type": "object"
  },
  "contractType": {
   "enum": [
    "spl_escrow",
    "cnft_badge",
    "raydium_vault"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "success": true,
  "signature": "5xyz...",
  "contractType": "spl_escrow"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/warppay402-deploy-solana-contract-0ea5b5de/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)