canonical: https://jentic.com/apis/databricks.com/databricks # Databricks API de Recherche d'Adresse de RC The Databricks RC Address Search API finds collective residences near a location by querying a Databricks SQL warehouse. It accepts a street address with a search radius, an X/Y geographic point with a radius, or a registration identifier, and returns the matching residences. Each result carries the residence's full characteristics and its distance in metres from the reference point. ## For AI agents Find collective residences near an address or geographic point, or resolve one by registration identifier, and get each match with its distance in metres. Backed by a Databricks SQL warehouse query. ## Scope Does not handle routing, turn-by-turn directions, or map rendering. Use for proximity search of collective residences near an address or point only. ## Capabilities - Find collective residences near a postal address within a given radius - Search collective residences around an X/Y geographic point within a radius - Resolve a collective residence directly by its registration identifier - Return each match with its full characteristics and distance in metres ## Use cases ### Agent-Driven Proximity Search An AI agent connected through Jentic can find collective residences near a location without a developer wiring the SQL call: it sends a street address and a radius and reads back the matching residences, each with its characteristics and distance in metres. Because the query runs against a Databricks SQL warehouse, the agent gets ranked, structured results it can act on directly. Example prompt: Search for collective residences within 500 metres of a street address and return each match with its distance ### Coordinate-Based Lookup When an agent already has coordinates rather than an address, it can search around that point. The API takes an X/Y point and a radius and returns the collective residences inside it, with their full characteristics. This suits workflows that start from a map pin or a geocoded location. Example prompt: Find all collective residences within a radius of a given X/Y point and list their characteristics ### Direct Registration Resolution Where a residence's registration identifier is already known, the API resolves it directly instead of searching by location. This returns the single residence's full record, which an agent can use to confirm or enrich an existing reference. Example prompt: Resolve a collective residence by its registration identifier and return its full record ## Key resources - **Residence Search** — Search collective residences by address, by X/Y point, or by registration identifier, returning distance and characteristics. ## 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:** 0 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 90 / 100 - Developer Experience & Jentic Compatibility: 60 / 100 - AI-Readiness & Agent Experience: 51 / 100 - Agent Usability: 94 / 100 - Security: 75 / 100 - AI Discoverability: 0 / 100 - **View full report:** https://jentic.com/apis/databricks.com/databricks/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 this API by hand means handling its bearer JWT and the Databricks SQL statements endpoint, then shaping each search as a request to the SQL warehouse. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The API exposes a single read-only search operation, so a rule bounds your agent to exactly that call and nothing else. Because the target address or point travels in the request body, rules bound which operation runs rather than which location is queried. - **Credential handling:** Your 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 addresses near a point', and Jentic returns the matching search operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Acuris Geo** — Geocoding that converts addresses to coordinates and back. - **Amadeus Points of Interest** — Finds points of interest near a set of coordinates. - **Country State City API** — Reference data for countries, states, and cities. ## FAQ ### What authentication does the Databricks RC Address Search API use? The API authenticates with a bearer token per its OpenAPI spec: you send an Authorization header carrying a JWT when calling the search endpoint. Through Jentic the token is stored once, encrypted, by your own Jentic One instance and injected at call time. ### Can I search for residences near a coordinate with the Databricks RC Address Search API? Yes. The search endpoint accepts a street address with a radius, an X/Y point with a radius, or a registration identifier, and returns the matching collective residences with their characteristics and the distance in metres from the reference point. ### What are the rate limits for the Databricks RC Address Search API? The OpenAPI spec does not define rate limits for this API. Because it runs against a Databricks SQL warehouse, check the Databricks SQL documentation at https://docs.databricks.com for query and concurrency limits. ### Is there a Databricks RC Address Search MCP server? You don't need an MCP server to give your agent this address-search API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent runs the search. Operations are discovered on demand without loading another server's tool definitions into context. ### Can I limit what my agent is allowed to do with the Databricks RC Address Search API? Yes. This API exposes a single read-only search operation, so a rule can allow exactly that one operation and nothing else, and because it only reads it cannot modify any data. Every call the agent makes is logged. ### How do I search for residences with the Databricks RC Address Search API through Jentic? Search Jentic for 'find residences near an address', and it returns the matching search operation with its input schema. Your agent sends the address and radius and reads back the ranked residences and their distances. To run it on your own infrastructure, install Jentic One from its GitHub repo.