Build with Prospectory
Integrate directly with Prospectory's tenant-scoped API for Lead Packs, Account Intelligence, sandbox testing, and MCP-enabled agent workflows.
Lead Packs
Create, list, update, and delete lead-pack containers used by Prospectory campaigns and integrations.
Account Intelligence
Create companies, retrieve enriched snapshots, and request async sync or AI enrichment workflows.
MCP server
Connect AI agents through the Prospectory MCP endpoint backed by the same tenant-scoped API services.
Quickstart
Create or choose an API key
Generate a server-side key in Prospectory and store it outside client-side code.
Start in sandbox
Use the sandbox base URL to validate request shapes without touching production workspace data.
Create Account Intelligence records
POST to /intelligence-companies with company names and websites. Enrichment starts asynchronously.
Poll for enrichment
Read records by ID until status moves from NOT_FETCHED to FOUND or NOT_FOUND.
Connect agents through MCP
Point an MCP client at /api/v1/mcp with the same x-api-key header to use the tool catalog.
Resource Map
Product names, REST paths, and MCP tools intentionally map to the same tenant-scoped resources.
/lead-packsprospectory_list_lead_packs, prospectory_get_lead_pack, prospectory_create_lead_packLead-pack containers organize leads for campaigns and integrations.
/intelligence-companiesprospectory_list_account_intelligence, prospectory_get_account_intelligence, prospectory_create_account_intelligence, prospectory_sync_account_intelligenceThe path keeps the historical API name, but the product feature is Account Intelligence.
/mcptools/list, tools/callJSON-RPC endpoint for MCP clients and AI agents, backed by the same tenant-scoped services.
Authentication
Public API requests use the x-api-key header. Keys are tenant-scoped, server-side credentials that restrict reads and writes to the issuing Prospectory workspace.
curl -X GET "https://api.prospectory.ai/api/v1/lead-packs" \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json"Production
https://api.prospectory.ai/api/v1Sandbox
https://api.prospectory.ai/api/sandbox/v1Returns dummy data for testing
Access Control
Public API keys are workspace-scoped. The API never returns resources from another Prospectory tenant.
API keys are scoped to one Prospectory workspace.
List and detail endpoints only return resources owned by that workspace.
Write endpoints create, update, sync, or delete resources inside that workspace only.
Use the sandbox base URL for integration tests that should not affect production data.
API Reference
Health Check
Monitor system health and infrastructure status.
Prospectory MCP Server
Prospectory exposes an MCP server on top of the same tenant-scoped API contract so AI agents can safely read Lead Packs, inspect Account Intelligence records, and request approved enrichment workflows.
https://api.prospectory.ai/api/v1/mcpAvailable Tools
prospectory_list_lead_packsList Lead Packs in the authenticated workspace.
prospectory_get_lead_packRetrieve one Lead Pack by ID.
prospectory_create_lead_packCreate a Lead Pack container without starting outreach.
prospectory_list_account_intelligenceList Account Intelligence records with filters and pagination.
prospectory_get_account_intelligenceRetrieve one Account Intelligence record and snapshot.
prospectory_create_account_intelligenceCreate Account Intelligence records and start async enrichment.
prospectory_sync_account_intelligenceRequest sync or AI re-enrichment for selected records.
prospectory_delete_account_intelligenceDelete one Account Intelligence record after explicit confirmation.
Call a Tool
curl -X POST "https://api.prospectory.ai/api/v1/mcp" \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "prospectory_list_account_intelligence",
"arguments": {
"page": 1,
"limit": 10,
"status": "FOUND"
}
}
}'Initialize
curl -X POST "https://api.prospectory.ai/api/v1/mcp" \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"protocolVersion": "2025-06-18",
"capabilities": {},
"clientInfo": {
"name": "example-agent",
"version": "1.0.0"
}
}
}'List Tools
curl -X POST "https://api.prospectory.ai/api/v1/mcp" \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/list"
}'Agent Safety Model
MCP uses the same workspace-scoped API key as REST. Read tools only see the authenticated workspace. Create and sync tools do not start campaigns, outreach, AI message generation, or Apollo imports. The delete tool is intentionally explicit and should only be called after user confirmation in the MCP client.
Error Handling
All errors follow a standardized format with error code, message, and optional details.
VALIDATION_ERRORRequest validation failedBAD_REQUESTInvalid request formatUNAUTHORIZEDMissing or invalid API keyFORBIDDENInsufficient permissionsNOT_FOUNDResource not foundRATE_LIMIT_EXCEEDEDToo many requestsINTERNAL_SERVER_ERRORServer errorSERVICE_UNAVAILABLEService temporarily unavailableError Response Format
{
"error": {
"code": "VALIDATION_ERROR",
"message": "Human-readable description",
"details": {
"field": "Additional context"
}
},
"timestamp": "2024-01-15T10:30:00Z",
"path": "/api/v1/lead-packs"
}Ready to integrate?
Get your API key and start building against Prospectory's tenant-scoped public API.