DEVELOPER ACCESS
Choose your integration path.
Reach one current, source-backed opportunity quickly, then follow the guide for the surface your application can support.
Start with the task
Use REST for backend services, scripts, and approved cross-origin browser reads.
Open the API guide →Remote MCP
Connect an MCP-compatible client to three read-only opportunity tools and one matching prompt.
Use remote MCP when an assistant can connect to a Streamable HTTP server.
Open the MCP guide →Data and exports
Understand the existing JSON and CSV compatibility export, its provenance, and its limits.
Use the export for a bounded snapshot; use REST or MCP for interactive discovery.
Open the Data guide →Use this guide when an agent or browser needs capability detection and a safe fallback.
Open the Agents guide →Public-read boundary
Endpoints listed in the public OpenAPI document require no authentication. The examples send no API key, Authorization header, or cookies.
Undocumented internal /api/v1/admin/* and /api/v1/agent/* namespaces are not public integration surfaces.
The public REST, remote MCP, and discovery surfaces are read-only. They do not submit applications, edit records, or grant access to review tools.
Verify the service
Use the live specification and discovery documents as the contract. The human guides explain first success, browser constraints, privacy, and recovery without replacing those machine-readable sources.