GPT Action Onboarding

Geo Lookup API publishes a plugin-style manifest and canonical OpenAPI contract.

AI-vibe coding friendly geolocation API with deterministic JSON, OpenAI compatibility artifacts, and Bearer token security.

Use POST /v1/public/lookup for one guest demo lookup per UTC day, POST /v1/lookup for Bearer-authenticated single lookups, and POST /v1/batch/lookup only when the caller's plan allows batch access. Always pass include fields explicitly for city, ASN, timezone, coordinates, or provenance. Prefer /openai.json or /.well-known/ai-plugin.json for discovery, but treat /openapi.json as the canonical machine contract.

Download OpenAPIView ai-plugin.jsonView openai.jsonView manifest.json

Discovery Paths

AI plugin
/.well-known/ai-plugin.json
OpenAI compatibility index
/openai.json
Machine manifest
/manifest.json
Canonical OpenAPI
/openapi.json
LLM index
/llms.txt
LLM index (full)
/llms-full.txt
This page
/docs/gpt-actions

Auth Model

  • Machine access uses HTTP Bearer authentication.
  • Guest lookup remains limited to one successful public lookup per UTC day.
  • Plan gating controls city, timezone, coordinates, batch lookup, and provenance.
  • OpenAPI remains authoritative; `openai.json` and `manifest.json` are compatibility wrappers.

Setup Steps

  1. Fetch either `/.well-known/ai-plugin.json` or `/openai.json` as the discovery entrypoint.
  2. Use the manifest's OpenAPI URL as the authoritative schema for GPT Actions and SDK generation.
  3. Authenticate machine requests with `Authorization: Bearer <api_key>`.
  4. Use `/v1/public/lookup` only for one guest demo lookup per UTC day.
  5. Use `/v1/batch/lookup` only when the caller's plan includes batch access.