Remote MCP
In a client that supports remote Streamable HTTP MCP servers, add this URL. Public discovery requires no account or token.
https://datap.app/mcp
Available tools: datatap_search_datasets, datatap_inspect_dataset, and datatap_get_access_instructions, and datatap_prepare_guest_access.
Keep paid decisions explicit
Your agent can prepare a guest quote and send you its approval link. Verify your email in that page, review the license and exact total, then complete hosted payment if needed. No account is required for a guest purchase. The agent keeps a separate collection token; never share that token. Guest scans are limited to sources up to 64 MiB; larger datasets require account authorization.
Connect your workspace
For recurring use, connect the protected endpoint below. Compatible remote clients use OAuth with PKCE and explicit workspace consent. You can also create a scoped, expiring token in Settings. Revoking it removes access immediately.
https://datap.app/mcp/private
Protected tools prepare quotes and read your jobs and orders. They cannot approve payments. OAuth consent, card setup and paid-update approval are separate decisions. API clients send tokens in the Authorization header, never a URL. The server uses stateless Streamable HTTP; protocol 2025-11-25 is covered by our local compatibility tests.
Collect a guest purchase
GET https://datap.app/api/v1/guest-access/status Authorization: Bearer $COLLECTION_TOKEN GET https://datap.app/api/v1/guest-access/download Authorization: Bearer $COLLECTION_TOKEN
After fulfilment, sign in with the verified purchase email and use the approval page to save the purchase to your workspace. Existing record ownership is merged, so later purchases do not charge for the same acquisition again.
Never paste payment details or private credentials into a conversation. Use hosted payment pages for billing.