Skip to main content

​
OpenAPI spec

The API publishes an OpenAPI 3.1 spec. It needs no key.

openapi.json

https://api.pav.bio/v1/openapi.json
It covers every /v1 endpoint with parameters, enums, limits, response schemas and the bearer security scheme. Use it to:
  • Generate a typed client with openapi-generator or openapi-typescript.
  • Import the API into Postman, Insomnia or Bruno.
  • Validate requests and responses in tests.
  • Give an agent a complete, current description of every endpoint.
The API Reference tab of this site is generated from the same spec.

​
Agents: MCP or REST

Both use the same Pav API key, return the same JSON, and share the same rate limit.

​
Tips for agent builders

  • Resolve names to ids first: list_companies (or GET /v1/companies?q=) returns company_id, which every other dataset filters on.
  • Pass phases as labels (Phase 3), not tokens. See Search and filters.
  • Keep limit small (5–25) in agent loops. Responses for programs and trials carry nested trials and outcomes and can be large.
  • Cite source_url, nct_url, deal events[].source_url and patent numbers back to the user. Every record carries its source.
  • Treat a missing field as “not disclosed”, not as false or zero. Fields with no value are omitted.