# Prysm Spoonacular Provider — Recipe & Food Data API

> Prysm Spoonacular Provider — Recipe & Food Data API is a paid API for AI agents from prysm-kappa.vercel.app, paid per call via x402, $0.07/call, status unknown (last checked 2026-10-14).

Proxies Spoonacular food and recipe data operations through Prysm's x402 micropayment gateway on Base mainnet, allowing agents to search recipes, get nutritional info, and access food data for $0.07 USDC per call.

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/spoonacular?utm_source=zero.xyz
- Price: $0.07/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-spoonacular-provider-recipe-food-data-api-3f514ddc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_O-nGN5M6PKfJf3iZf0r26

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 prysm-spoonacular-provider-recipe-food-data-api-3f514ddc -d '<json body>'
```

Example prompt: Search Spoonacular for quick vegetarian pasta recipes with under 500 calories — use the recipes operation and filter for vegetarian diet.

## When to prefer this

Choose this endpoint when you need Spoonacular's food and recipe data in an agent workflow that already uses x402 micropayments on Base mainnet with USDC, and you want to avoid managing a separate Spoonacular API key. Ideal for autonomous agents that need pay-per-call recipe lookups without subscription overhead.

## Known failure modes

- Invalid or unsupported operation name returns an error — only allowlisted Spoonacular operations are accepted
- Malformed input parameters for the chosen operation may result in empty results or an error from Spoonacular's API
- Payment failure on Base mainnet (insufficient USDC, x402 handshake failure) blocks the request entirely
- Rate limiting or quota exhaustion on Spoonacular's backend may cause upstream errors
- Missing required input fields for the specific operation result in a validation error

## How this service works

Prysm sells paid, agent-ready provider capabilities over x402 on Base mainnet using USDC.

## Output

Returns a JSON object with a `data` field containing Spoonacular's response (recipes, nutritional data, ingredient info, etc.), a `provider` field set to 'spoonacular', and an `operation` field indicating which Spoonacular operation was called.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "description": "Provider-specific operation parameters.",
   "additionalProperties": true
  },
  "operation": {
   "type": "string",
   "description": "Allowlisted operation for the selected provider."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "provider": "spoonacular",
  "operation": "recipes"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-spoonacular-provider-recipe-food-data-api-3f514ddc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from prysm-kappa.vercel.app](https://www.zero.xyz/host/prysm-kappa.vercel.app/llms.txt)