# Prysm PostHog Provider

> Prysm PostHog Provider is a paid API for AI agents from prysm-kappa.vercel.app, paid per call via x402, $0.08/call, status unknown (last checked 2026-10-22).

Proxies PostHog analytics operations (e.g. event capture) through Prysm's x402-gated API, payable in USDC on Base mainnet.

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/posthog?utm_source=zero.xyz
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-posthog-provider-b8081cee
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_18fC-Puh31bdAwaD0-NI8

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-posthog-provider-b8081cee -d '<json body>'
```

Example prompt: Send a 'checkout_completed' event to PostHog for user 'user_abc123' with properties order_value: 49.99 and currency: 'USD' using the capture operation.

## When to prefer this

Choose this endpoint when your AI agent needs to send PostHog analytics events (such as event capture) in a Web3-native, pay-per-call fashion using USDC on Base, without managing PostHog API keys or credentials directly. It is ideal for agent pipelines that already use x402 for micropayments and want to instrument user or agent behavior in PostHog without standing up a separate backend integration.

## Known failure modes

- Invalid or unsupported operation name returns an error — only allowlisted PostHog operations are accepted
- Missing required input fields for the chosen operation may cause a PostHog-side rejection
- Payment failure or insufficient USDC balance prevents the call from being processed via x402
- Malformed input object properties may result in a PostHog validation error surfaced in the data field
- Network or PostHog API downtime can cause transient failures

## How this service works

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

## Output

A JSON object containing the provider name ('posthog'), the operation executed (e.g. 'capture'), and a data field with the raw PostHog API response confirming the operation result.

## 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": "posthog",
  "operation": "capture"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-posthog-provider-b8081cee/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)