GR Global Reach API
checking…

API Playground

Build a request, run it against the live API, and copy working code in your language.

Stored in this browser only. Keys are minted on the policy tier: php bin/console app:key:create "my-client" on the processor host — tokens are hashed, so a lost one is rotated, not recovered.


Sealed before leaving this service; responses identify jobs by fingerprint, never by term.

1 page · 10 results · 1 Google request

de/fr/it rank differently

Result localisation

No location parameter is sent. Google falls back to whatever the agent's exit IP looks like, which is country-accurate and rarely better.

Direct leaves via the agent host's own egress — on this fleet, the AWS instance IP. Measured 2026-08-29: it scored 36/36 on a warm profile where the residential proxy scored 0/8. It overrides location-based identity choice rather than narrowing it, which is safe now that uule and coordinates do the localising — the exit no longer decides where the SERP thinks you are.

A hard pin: no other agent may serve it. If that agent is busy or offline the job waits queued rather than being routed elsewhere — leave empty unless you mean that. An unregistered id is refused at submit.

The same pin one level finer: one browser, one profile, one exit IP. You need not also name the agent — the fleet roster says which host owns the identity. Paste a token above and the list fills in from GET /v1/agents; every result also reports which identity served it, so a run you liked can be repeated on the same one.

Advanced parameters

qdr:h · qdr:d · qdr:w · qdr:m · qdr:y

Results are POSTed here when the job finishes.

Run a search to see results here.

// The API response will appear here.