Developer access
Build on the same geolocation workflow that powers the product.
Generate and manage API keys, inspect usage, and integrate the photo geolocation pipeline into your own applications with a clearer request path and a confidence-aware response model.
Usage snapshot
One surface for access, usage, and request readiness.
0
active API keys
0
total requests
10,000
combined monthly capacity
0%
current usage rate
API keys
Manage authentication and usage.
Create separate keys for production, staging, or experiments. Keys are shown here so they can move directly into your environment and deployment flow.
Quick start
Send an image and receive a structured geolocation result.
This is the shortest path from key issuance to a working request. Use it to validate auth, payload shape, and the live response contract before wiring the rest of your product around it.
Endpoint
https://pic2nav.com/api/location-recognition-v2curl -X POST https://pic2nav.com/api/location-recognition-v2 \
-H "Authorization: Bearer YOUR_API_KEY" \
-F "image=@photo.jpg"Request flow
Issue a key for the environment you control
Keep production, staging, and experiments separate so usage remains attributable and keys are easy to rotate later.
Call the same route used by the product workflow
The API follows the live recognition stack: direct evidence first, then retrieval, scene reasoning, and route-side validation.
Handle confidence-aware output instead of guessing
The response is designed to fail closed when evidence is weak, so your integration can decide how to escalate or ask for another image.
Documentation
What you get
Structured coordinates, address context, method provenance, and enrichment fields in one response.
The same production workflow surfaced in the camera demo, not a separate toy endpoint.
A system that can connect future feedback and training rather than a one-off model call with no memory.