Gisgraphy webservices
48
AI ReadinessFoundational (D+)48/100
Official vendor OpenAPI document · agent-readyMaps GeolocationGeocodingapiKey6 EndpointsREST
For Agents
Geocode addresses, reverse-geocode coordinates, parse address strings, and search for nearby places using Gisgraphy's open-source webservices.
Use for: Geocode the address '10 Downing Street, London', Reverse geocode the coordinates 48.858 2.294 to find the nearest address, Parse the string '1600 Pennsylvania Ave NW Washington DC' into components, Search for cities matching 'Springfield'
Not supported: Does not handle turn-by-turn directions, traffic data, or map tile rendering - use for geocoding, reverse geocoding, address parsing, and place search only.
Gisgraphy is an open-source geocoding and geolocation framework that exposes REST webservices for forward and reverse geocoding, address parsing, full-text search, nearby place search, and street lookup. Data comes from OpenStreetMap, GeoNames, and Quattroshapes - over 100 million entries - making it a free alternative to Google Maps and Mapbox. Output formats include JSON, XML, PHP, Python, Ruby, YAML, GeoRSS, and Atom, and optional premium servers accept an api_key for higher quotas.
Install Jentic One Beta
Connect the Gisgraphy webservices to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Gisgraphy webservices, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgisgraphy.com%2Fgisgraphy" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgisgraphy.com%2Fgisgraphy" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Gisgraphy webservices API.
Geocode a street address into latitude and longitude via /geocoding/geocode
Reverse-geocode a lat/lng pair into the closest address via /reversegeocoding/reversegeocode
Parse free-form address strings into structured components via /addressparser/parse
Search for places, cities, and points of interest via /fulltext/search
Find features near a coordinate within a radius via /geoloc/search
Resolve street and segment metadata via /street/find
Use Cases
Patterns agents use Gisgraphy webservices API for, with concrete tasks.
★ Address Form Autocomplete
Power a checkout or signup form with structured address suggestions backed by OpenStreetMap data. The /fulltext/search endpoint returns places matching a partial query, and /geocoding/geocode resolves the chosen suggestion into precise coordinates for delivery routing.
Call /fulltext/search with q='1600 Pennsylvania' and country=US, then geocode the top suggestion via /geocoding/geocode
Delivery and Logistics Routing
Convert customer-supplied addresses into coordinates for routing and dispatch. /geocoding/geocode returns lat/lng plus admin-level breakdown, and /reversegeocoding/reversegeocode resolves driver pings back into human-readable street addresses for delivery proof.
Reverse-geocode lat=51.5034 lng=-0.1276 via /reversegeocoding/reversegeocode and return the formatted street address
Local Search for a Mobile App
Show points of interest near a user's location in a mobile app. /geoloc/search accepts a lat/lng centre and a radius, returning OpenStreetMap features sorted by distance - restaurants, parks, transit stops - without licensing fees from a commercial maps provider.
Call /geoloc/search with lat=40.7128 lng=-74.0060 radius=500 and placetype=Restaurant; return the names of the five closest results
AI Agent Address Parsing
Let an AI agent normalise free-form address strings collected from email, chat, or scraped data. The agent issues an intent like 'parse a postal address', Jentic resolves the /addressparser/parse call, executes it, and returns structured fields the agent can validate or store.
Through Jentic, call /addressparser/parse with address='Apt 4B 221 Baker Street London NW1' and return houseNumber, streetName, and city
Key Endpoints
6 endpoints — gisgraphy is an open-source geocoding and geolocation framework that exposes rest webservices for forward and reverse geocoding, address parsing, full-text search, nearby place search, and street lookup.
METHOD
PATH
DESCRIPTION
GET
/geocoding/geocode
Forward geocode an address to coordinates
GET
/reversegeocoding/reversegeocode
Reverse geocode coordinates to an address
GET
/addressparser/parse
Parse a free-form address string
GET
/fulltext/search
Full-text search across places and admin areas
GET
/geoloc/search
Find features within a radius of a coordinate
GET
/street/find
Look up street segments
GET
/geocoding/geocode
Forward geocode an address to coordinates
GET
/reversegeocoding/reversegeocode
Reverse geocode coordinates to an address
GET
/addressparser/parse
Parse a free-form address string
GET
/fulltext/search
Full-text search across places and admin areas
GET
/geoloc/search
Find features within a radius of a coordinate
GET
/street/find
Look up street segments
Jentic AI Readiness Score
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.
G
Gisgraphy webservices
- Foundational (D+)48/100
72
Foundational Compliance69
Developer Experience & Jentic Compatibility56
AI-Readiness & Agent Experience94
Agent Usability15
Security58
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
72
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
89%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
69
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
56
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
74%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
58
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C+Signals: 1
58%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Gisgraphy by hand means passing an api_key in the query string for premium servers, choosing between the free and premium hosts, and formatting geocoding parameters yourself. Through Jentic you install once, import Gisgraphy from the API Directory, store the key once for premium use, and your agent calls it.
Permission scoping
Gisgraphy carries its query and coordinates in the request parameters rather than a resource id in the URL path, so scope the agent to the operations it needs, such as geocoding an address or parsing one. You choose the allowed operations, so wider ones like reverse geocoding or place search are only available if you include them.
Credential isolation
Your Gisgraphy api_key is stored once, encrypted, by your own Jentic One instance and injected at execution time, while the free server can be called with no credential. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'geocode an address' or 'parse a postal address', and Jentic returns the matching Gisgraphy operation with its query-parameter schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Positionstack API
Forward and reverse geocoding with 25k free monthly requests
Choose Positionstack when a hosted commercial geocoder with a clear monthly free quota fits the project better than self-hosted Gisgraphy.
FAQs
Specific to using Gisgraphy webservices API through Jentic.
What authentication does the Gisgraphy API use?
The free server at free.gisgraphy.com is open and does not require credentials. Premium servers accept an api_key query parameter for higher quotas. Through Jentic the api_key is stored encrypted in your Jentic One instance and only injected at execution time.
Can I geocode an address with the Gisgraphy API?
Yes. Call GET /geocoding/geocode with address and country to convert a postal address to coordinates. The response includes lat, lng, formatted address, and the matched admin levels (city, state, country) drawn from OpenStreetMap data.
What are the rate limits for the Gisgraphy API?
The free tier on free.gisgraphy.com is best-effort and may throttle aggressive clients without a fixed published cap. Production deployments should host Gisgraphy themselves or use the premium servers, which are sized to the subscription tier.
How do I reverse-geocode coordinates through Jentic with Gisgraphy?
Search Jentic for 'reverse geocode coordinates', load the GET /reversegeocoding/reversegeocode schema, and execute with lat and lng. The response returns the closest street address along with admin-level fields drawn from the underlying OpenStreetMap dataset.
What data does Gisgraphy use under the hood?
Gisgraphy ingests OpenStreetMap, GeoNames, and Quattroshapes - more than 100 million entries - into a Solr-backed search index. That makes it suitable for a Google-Maps-free or Mapbox-free deployment when licensing is the dominant constraint.
Is the Gisgraphy API free?
Yes. Both the framework and the free public server are released under an open-source licence with no usage charge. Paid premium servers exist for users who need higher quotas, an SLA, or commercial support beyond what the open community endpoint provides.
Can I limit what my agent is allowed to do with the Gisgraphy API?
Yes. Because Jentic One is self-hosted, you decide which Gisgraphy operations your agent may call, so you can allow narrow ones like forward geocoding an address or parsing a postal string while withholding wider ones such as reverse geocoding coordinates or nearby place search. Since Gisgraphy carries its query and coordinates in request parameters rather than a resource id in the URL path, scoping is done at the operation level and an operation is only reachable if you include it. Your own rules also govern the api_key used for premium servers, which stays under your control and is injected only at execution time.
GET STARTED