SELF-DECLAREDNO LOGINMACHINE-READABLEOPEN SOCIAL
How it works
Post once.
Be findable anywhere.
- 01
Send a flare
Mention @whereis.co on Bluesky with a location, such as @whereis.co Lisbon #whereis. Be as exact or vague as you want.
- 02
We publish your endpoint
Your permanent page and JSON endpoint update. There is no account, app, or location permission.
- 03
Share the signal
Put it in a bio, email footer, travel page, or give the API to an agent. Your original post stays attached as proof.
Usage guide
Send a flare.
Keep the URL.
Updates come from the Bluesky identity they describe. The resulting page works for people, scripts, and agents—with no WhereIs account or API key.
For people
Update from Bluesky
01Post your location
@whereis.co Sydney, AustraliaMention @whereis.co from your own account. Exact, broad, and playful locations are all valid.
02Use your permanent link
https://whereis.co/your.handleThe bot replies with this URL within about five minutes. Share it once; it stays the same.
03Update—or clear—it
Post a new mention to replace the current location. To remove your signal, post:
@whereis.co #whereis-off
For agents and apps
Read the public API
Use the handle without a leading @. Reads are public, CORS-enabled, and require no API key.
Terminal
curl https://whereis.co/api/v1/location/cje.io
200Current self-declared signal, source, timestamp, and age.
404Unknown, empty, or opted-out handle with found: false.
View live JSON →
For agents, apps, and curious humans
One obvious endpoint.
GET https://whereis.co/api/v1/location/alice.example
{
"found": true,
"handle": "alice.example",
"location": "Lisbon for the week",
"publishedAt": "…",
"sourceUrl": "https://bsky.app/…",
"ageSeconds": 64
}
The boundary matters
WhereIs.co says what people said—not where devices are.
No GPS collection. No IP geolocation. No background tracking. No third-party claims. A person can post #whereis-off to clear their signal.