AP AP

AI Proxy / Public Rendezvous

Give a private application a public HTTPS URL.

A private app connects outward to AP, and AI clients call it like any web API. No inbound port, no VPN, no tunnel agent.

PUBLIC / CLIENT SIDE AP / PUBLIC RENDEZVOUS PRIVATE / APP SIDE AI CLIENTS AI CLIENTS AI CLIENTS REQUEST · HTTPS RESPONSE · SAME CHANNEL OUTBOUND POLL QUEUED REQUEST APPLICATION RESPONSE STABLE PUBLIC NAMESPACE /c/{channel} AP APPLICATION APP-OWNED ROUTES /.../projects/...
AP in motion: an AI client's request reaches AP and waits in its queue. AP cannot reach the private application, so the application polls outward to AP, and the waiting request is delivered as the answer to that poll. The response returns through the same channel.

An AI client, agent or service calls the public endpoint. AP hands each request to the private app and returns its response. AP routes intelligence. It does not provide intelligence.

Get started

ExamplePut a tiny app online in five steps. READMEThe API overview and how channels work. AccountsSign in with Google or GitHub to get an AP key.

Signing in

An AP key proves who you are. You get one by signing in with a Google or GitHub account through the device flow, which asks for a short code and gives you a key once you approve it. See the privacy policy for what AP keeps.

AP is open source. Source, issues and documentation are on GitHub.