Phone metadata for agents
Phone metadata attached to agent mobile identity.
Show assigned SIM phone metadata beside the same physical device, real SIM, carrier mobile IP, and route health used by browser agents.
GatePilot mobile identity
Phone metadata belongs to the agent identity.
GatePilot displays assigned SIM phone metadata with the same mobile device and carrier network identity your browser agent uses.
Assigned phone metadata
Keep available phone metadata attached to the assigned SIM-backed mobile identity instead of a disconnected record.
Persistent proxy identity
Keep browser traffic attached to the same real SIM-backed mobile identity and carrier route.
Operational visibility
Keep phone metadata and browser route health tied to the assigned device lifecycle.
The short answers searchers and AI assistants need.
Core facts for teams evaluating physical mobile identity, carrier routing, assigned phone metadata, route health, and session visibility for AI agents.
What is GatePilot?
GatePilot gives production AI agents dedicated mobile proxy identities: physical mobile devices, real SIMs, carrier mobile IPs, assigned phone metadata, and route health.
How is this different from a mobile proxy?
A mobile proxy routes traffic. GatePilot assigns a stable mobile identity that includes the device, SIM, carrier mobile IP, assigned phone metadata, and route health.
Does each agent get phone metadata?
The assigned SIM can include phone metadata for the identity, but inbound SMS and phone workflows are not part of the launch pilot.
Does it work with Playwright or Browserbase?
Yes. GatePilot works with Playwright, Puppeteer, Browserbase, and agent stacks that can use an authenticated session route.
What countries are available?
United States is available today. Additional countries are handled through design partner requests and should be treated as waitlist availability until provisioned.
Phone identity package
Common questions.
Can the same agent keep the same number?
GatePilot is designed for persistent assignment, so available SIM phone metadata stays attached while the identity is active. SMS workflows are not part of the launch pilot.
Is this separate from browser identity?
No. GatePilot ties available phone metadata to the same assigned mobile identity that carries the browser session and carrier network path.