PremiumPin API Documentation

Quickstart

Use hosted MCP with Google OAuth in a compatible agent, or connect through HTTPS API and the optional local MCP client.

For scripts and compatible agent clients, create a key on the account service after checkout. Send it in the Authorization header using the Bearer scheme. Never put a key in a URL, conversation, or shared configuration. Search posts to /v1/query; CSV posts to /v1/export. Paid accounts can ask unlimited questions and receive 1,000,000 delivered parcel rows per UTC month, with 5,000 rows per export. Responses return all available fields, up to 91. Request shape and field rules are on API + agents.

Hosted and local MCP

The hosted endpoint exposes the same curated tools as the download and carries requests through the existing API controls. OAuth sign-in is live for ChatGPT, Claude, Claude Code, Codex, and Cursor. Clients that support private headers may instead use a Bearer API key.

After install, run python -I -B -m premiumpin_customer or the premiumpin-mcp entry point over STDIO. Load the customer skill with your host’s local-skill mechanism. That path is the published CLI.

Machine discovery: OpenAPI 3.1, llms.txt, api-catalog, MCP server card, and agent-skills index. The server card lists both transports and the current authentication boundary.

Stable v1 contract

The current REST contract uses the /v1/ path. Additive fields and endpoints may ship within v1. Breaking request or response changes require a new major path.

When an endpoint is deprecated, PremiumPin will document the replacement and provide at least 90 days notice before removal. Deprecated responses will include the standard Deprecation and Sunset headers plus a Link to the policy. No v1 endpoint is currently deprecated. Read the full versioning and deprecation policy.

Compare parcel tools

For agent access, read LandRecords vs PremiumPin. Per-record list math is on the property list cost calculator.