For AI agents
Paranor exposes a stable, machine-readable Agent API per creator. Use it for content discovery, booking, media kits, and event-driven workflows. This page is a high-level guide; for full specs see the API docs and OpenAPI.
Discovery
For a single creator, start with GET {base}/api/agent. The response lists all endpoint URLs, version, capabilities (e.g. webhooks.v1, mcp.v1, l402.v1), openApiUrl, and changelogUrl. Prefer this over scraping. If llms.txt or the Agent Card is slow or unreachable, use the API index as the authoritative source. For multi-creator discovery by topic, call GET https://paranor.app/api/nexus/creators?topic=...; then use each creator’s agentBaseUrl for their API.
Health check: GET {base}/api/agent/health returns 200 and { "status": "operational" }. Use it before running workflows.
What you can do (free)
Without payment you can use: profile, content-index (with filters like ?tag=, ?digest=7d, ?count=true), booking, media-kit, speaking, discovery, health, webhook-subscribe, and booking-request. When L402 is enabled on an instance, some endpoints may return 402; you can then pay via Lightning or use Pay-or-Work (complete a micro-task for access) where offered.
Content and change detection
Use content-index with ?count=true or ?digest=7d for lightweight “has anything changed?” checks. Use conditional GET (If-None-Match / If-Modified-Since) to get 304 when unchanged. When the response has no items or count 0, check emptyReason (e.g. index_empty, filter, l402_required) so you can branch without guessing.
Webhooks and events
Subscribe via POST {base}/api/agent/webhook-subscribe with your callbackUrl and events (e.g. dot.approved, content.published, changelog.updated). The creator approves the subscription in Paranor. You then receive POSTs to your URL when those events occur. If the creator set a webhook secret, verify the X-Paranor-Signature header (HMAC-SHA256 of body).
Booking and outreach
Use GET .../booking for topics, sample questions, and one-liners. Submit requests with POST .../booking-request (showName, showUrl, message, source: "agent"). Creators see inbound requests in Paranor → Intelligence → Booking requests.
FAQs and instruction-style docs
We provide an AI Agent Instruction Book (in the project docs: AI_AGENT_INSTRUCTION_BOOK.md) with FAQs and copy-paste style instructions for discovery, content-index, webhooks, L402, rate limits, and MCP vs REST. Use it as additional context for your system prompt or tooling. The canonical API spec and OpenAPI are at each creator’s /agent and /api/agent/openapi.json.