Geocode one street address or reverse geocode one coordinate with your Geocodio self-serve key. Preserve source attribution and explicit result bounds.
What you can do (2)
What you can do
Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
Geocode one address — geocodio.geocode |
Read |
Reverse geocode one coordinate — geocodio.reverse |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Geocodio, then enter the issued values in the connection form below.
- Create or sign in to a Geocodio account and open https://dash.geocod.io/apikey. Create a self-serve API key with forward and reverse geocoding permissions. In Tooluse.net, open My tools > Geocodio > Use my provider credentials, paste it into Geocodio API key, select the commands and save. Use geocode with one address, a supported ISO country code and a result limit, or reverse with exactly one latitude,longitude pair. Requests use your Geocodio lookup allowance and billing; this subset does not request paid field appends, distance calculations or batches. Enterprise endpoint keys are a separate product and are not supported here.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Geocodio API key | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {
"query": {
"q": "1109 N Highland St, Arlington VA",
"country": "US",
"limit": 1
}
}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
Geocode one address — geocodio.geocode
Geocode one address using Geocodio v2.1. Returns bounded matches with coordinates, accuracy and source attribution. One lookup can consume your Geocodio quota; no field appends or batches.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.q |
string | Required | One street address to geocode. | minLength: 1; maxLength: 500; pattern: "^[^\\u0000-\\u001f\\u007f]+$" |
query.country |
string | Required | ISO country code for this address. | enum: ["US","CA","MX","GB","AU","NZ"] |
query.limit |
integer | Required | Maximum matching addresses returned for this single lookup. | minimum: 1; maximum: 5 |
Full JSON Schema
Example input
{
"query": {
"q": "1109 N Highland St, Arlington VA",
"country": "US",
"limit": 1
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Reverse geocode one coordinate — geocodio.reverse
Find address matches for one latitude/longitude pair using Geocodio v2.1. Returns accuracy and source attribution. One lookup can consume your quota; no field appends, distance calculations or batches.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.q |
string | Required | Exactly one decimal latitude,longitude pair in geographic ranges. | minLength: 3; maxLength: 60; pattern: "^-?\\d+(?:\\.\\d+)?,-?\\d+(?:\\.\\d+)?$" |
query.limit |
integer | Required | Maximum address matches for this one coordinate. | minimum: 1; maximum: 5 |
Full JSON Schema
Example input
{
"query": {
"q": "38.886672,-77.094735",
"limit": 1
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.