canonical: https://jentic.com/apis/angi.com/angi # Angi Pros API The Angi Pros API finds local home-service professionals. A single search operation takes a ZIP code and an optional service type and returns the matching pros in that area, so an agent can turn a homeowner's request into a shortlist of plumbers, electricians, cleaners, or other tradespeople near them. Results can be narrowed with free text and capped to a chosen number of pros. ## For AI agents Search Angi for local home-service professionals by ZIP code and service type. One read operation secured with a bearer token. ## Scope Does not handle booking, payments, or reviews - use it to search for local service professionals only. ## Capabilities - Search local service pros by ZIP code - Filter a pro search by service type - Narrow a pro search with free text - Limit the number of pro results returned ## Use cases ### Find local service pros Turn a homeowner request into a list of nearby professionals. The agent passes the ZIP code and the service it needs, then reads back the pros serving that area. Example prompt: Call GET /pros with the zip_code and service_id for the request ### Route a request to the right trade Match a free-text request to the right kind of professional. The agent supplies the request text alongside the ZIP code so the search returns pros relevant to the stated need. Example prompt: Call GET /pros with the zip_code and initial_text describing the job ### Build a shortlist of contractors Assemble a capped shortlist for a homeowner to choose from. The agent limits how many pros come back so it can present a tidy set of options. Example prompt: Call GET /pros with the zip_code, service_id, and limit set to the shortlist size ## Key resources - **Pros** — Local home-service professionals returned by the search - **Services** — The service type used to filter a pro search ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 73 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 83 / 100 - AI-Readiness & Agent Experience: 58 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 63 / 100 - **View full report:** https://jentic.com/apis/angi.com/angi/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Angi Pros API by hand means obtaining a bearer token, pointing at the api.angi.com host, and shaping the pro-search query yourself. Through Jentic you install once, import Angi from the Jentic API Directory, store the token once, and your agent calls it. - **Permission scoping:** The Angi Pros API exposes a single search operation, so scoping is about whether your agent may call it at all. You choose that in your own rules, and because the search is read-only it returns matching pros without changing anything. - **Credential handling:** Your Angi bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find local service pros near a ZIP code', and Jentic returns the Angi search operation with its input schema so the agent supplies the right query parameters. ## Related APIs - **Yelp** — Alternative local business search API - **Foursquare** — Alternative places search API - **OpenCage** — Complementary geocoding API ## FAQ ### What authentication does the Angi Pros API use? The Angi Pros API uses a bearer token in the Authorization header. Through Jentic, that token is stored encrypted in your Jentic One instance and injected at execution time, so the raw secret never enters the agent context. ### What can an agent do with the Angi Pros API? It can search for local home-service professionals by ZIP code and service type, narrow the search with free text, and cap how many pros come back. The response is structured so an agent can present or act on the matches directly. ### Can I search Angi pros by location? Yes. The search takes a ZIP code and returns pros serving that area, optionally filtered by the service type and a free-text description of the job. ### What are the rate limits for the Angi Pros API? Rate limits are not specified in the OpenAPI spec. Check the Angi documentation for current limits. Through Jentic, retries are handled in the execution layer. ### How many endpoints does the Angi Pros API have? The Angi Pros API exposes a single search endpoint that returns local service professionals. ### Can I limit what my agent is allowed to do with the Angi Pros API? Yes. Jentic One is self-hosted by you, so your own rules decide whether your agent may call the Angi search at all. The API exposes one read-only search operation and no write operations, so the agent can look up pros but cannot change any data.