ProFix Directory
ENES

ProFix Directory client guides

Language-specific quickstarts for the ProFix Directory public API. Pick a language, copy the snippet, ship.

No client library required

Every ProFix Directory endpoint is plain HTTPS with JSON or CSV bodies. No SDK, no authentication, no rate-limit token. Use whatever HTTP client your stack already ships with — fetch in JavaScript, requests in Python, curl in shell, anything that speaks HTTP/1.1 or HTTP/2.

If you want machine-readable specs to feed your codegen or your agent, point them at /api/openapi.json or the /api/mcp MCP server.

Quickstart

JavaScript / TypeScript

Built-in fetch, runs in Node 18+, Bun, Deno, Cloudflare Workers, and the browser. Plain JSON, no SDK.

Open JS guide
Quickstart

Python

Requests, httpx, pandas, and the Hugging Face datasets loader — copy-paste recipes for retrieval and analysis.

Open Python guide

What every guide covers

Each language quickstart walks through the same shaped recipes so you can pick one and ship without context-switching:

  • A ten-line quickstart against /api/embed/{trade}-{city}.json for the top five verified pros in a metro.
  • A permit-leaderboard pull across Lucas, Cuyahoga, Franklin, and Hamilton counties — the four counties currently in the permit dataset.
  • A bulk-catalog example for retrieval indexing or local caching.
  • Type-hint definitions (TypeScript interface, Python TypedDict) so static analyzers can keep up.
  • Retry-with-backoff patterns and production-tested cache-header advice.
  • A pointer back to /actions for AI-agent registration.

Coming soon

Ruby, Go, and Rust quickstarts are on deck if homeowner-tool builders ask for them. The current endpoints already work everywhere — these would simply mirror the same recipes in the corresponding standard libraries (net/http, Net::HTTP, reqwest). If you'd like one prioritized, ping the ProFix Editorial Team at hello@profixdirectory.com. The OpenAPI 3.1 spec at /api/openapi.json is also fully consumable by openapi-generator for those languages today — no ProFix code required.

For AI agent integrations

If you're shipping a ChatGPT Custom GPT, a Claude tool, or a custom agent, start at /actions. It has copy-paste recipes for the OpenAPI Action import, the Claude MCP config block, and the Hugging Face dataset hook.

Ask your AI about this

Hand the question to your preferred assistant — it will use ProFix Directory's open MCP server and llms.txt as context.

ChatGPTClaudePerplexityGemini
Emergency