Getting started

Three steps to give your agent its first budget:

  1. Get an API key — request access at hello@pipavia.com. Keys are scoped to one owner account and can be rotated at any time.
  2. Point your agent at the MCP endpoint — any MCP-compatible client works. The marketplace directory lists every connector, tool schema, and per-call price in machine-readable form.
  3. Set a spending policy — define budgets, per-call caps, and connector allowlists. The policy engine signs a spending mandate your agent presents with each purchase.

Authentication

All API and MCP calls authenticate with a bearer API key in the Authorization header. Keys are never placed in prompts or tool arguments — they travel in headers only, and every key carries an owner identity the policy engine checks.

Authorization: Bearer pv_live_…

Spending-policy engine

The policy engine is Pipavia's core: it turns "my agent can spend money" into a controlled, auditable act. Before any purchase settles, the engine verifies a signed spending mandate against your rules:

If any rule fails, the purchase is blocked and the agent receives a machine-readable reason (e.g. budget_exhausted, connector_not_allowed) so it can adapt instead of failing silently. Every decision — allowed or denied — is written to an audit log you can export.

Tool reference — Filings & Fundamentals

Our first connector exposes SEC EDGAR filings and normalized fundamentals. Representative tools (the full schema ships with the connector):

ToolWhat it doesIndicative price
filings.searchSearch 10-K / 10-Q / 8-K filings by company, form, or keyword$0.01 / call
filings.get_financialsNormalized income statement, balance sheet, cash flow$0.02 / call
filings.get_ratiosMargins, returns, leverage, and liquidity ratios$0.02 / call
filings.get_segmentsSegment-level revenue and operating income$0.03 / call

Data freshness: within 48 hours of publication at the source (contractual SLA). Prices are machine-readable at the directory endpoint and may vary by plan.

Settlement & receipts

Pipavia settles on borrowed rails — x402/USDC for per-request micropayments and Stripe for subscriptions and credit packs. We are the merchant of record for our own connectors; we never take custody of customer funds and operate no proprietary settlement.

Every settled purchase emits a signed receipt: connector, tool, price, timestamp, and the mandate that authorized it. Receipts are your audit trail for agent spend.

Support

Free plan: community support. Pro and Team: email support with priority queueing for Team. Enterprise: dedicated support with custom SLAs. Contact hello@pipavia.com.

Security scans are published, the changelog is public, and connector source is open-core (Apache-2.0) — the policy engine, metering, and billing remain proprietary.