Give your agent a callback
Bring external events into the AI tools you're developing locally.
THE LOCAL-FIRST LAUNCH ROOM
Your next idea already runs on localhost.
Give it a way in from the rest of the world.
Connect AI agents, callbacks, and automations to your local app through one stable URL. Keep building where you work best.
Coming soon. Registration opens at launch.
https://my-agent.hooks.hokio.topPOST /api/webhook
Content-Type: application/json
{
"event": "message.created",
"data": { "text": "Hello, local app." }
}HTTP/1.1 200 OK
Content-Type: application/json
{
"received": true,
"handled_by": "your local app"
}localhost:8000Try a sample event. This demo runs in your browser.
MADE FOR WHAT YOU'RE BUILDING
AI agentsModel callbacksAutomationsWebhook integrations01 / THE CONNECTION
One connector bridges the gap between your app and the services that need to reach it.
Sign in to your Hokio workspace and connect your device.
Point the connector at the port your app listens on, such as 8000.
Add your permanent HTTPS address to a service that sends webhooks.
localhost:8000An AI callback travels through your Hokio URL to the app running on your machine.
Illustrated flow · no live trafficBUILT TO STAY
Restart your machine. Reconnect your app. Move between assigned tunnel servers. Your public webhook address stays the same.
my-agent.hooks.hokio.topPERMANENTThis URL stays the same while your endpoint remains assigned.
02 / YOUR STACK, YOUR WAY
Your code editor, language, and framework are up to you. If your app accepts an HTTP request, it can receive a webhook.
Bring external events into the AI tools you're developing locally.
Receive repository events and automation triggers before you deploy.
Edit, run, and inspect requests on the machine where you're building.
import express from 'express';
const app = express();
app.use(express.json());
app.post('/api/webhook', (req, res) => {
console.log(req.body);
res.json({ received: true });
});
app.listen(8000);from flask import Flask, request
app = Flask(__name__)
@app.post("/api/webhook")
def webhook():
print(request.json)
return {"received": True}
app.run(port=8000)# Replace with your assigned Hokio URL
curl -X POST \
https://my-agent.hooks.hokio.top/api/webhook \
-H 'Content-Type: application/json' \
-d '{"event":"message.created"}'03 / SET YOUR BOUNDARIES
Open a door to your app, then decide what gets through. Your administrator configures access rules for each endpoint.
Public webhook endpoints use HTTPS. Your local app can keep listening on its own HTTP port.
Allow trusted source IPs, select HTTP methods, and restrict accepted request paths.
Bound request rates, payload sizes, and concurrent requests for your endpoints.
Use your app to verify provider signatures, such as GitHub or payment webhooks.
04 / ON YOUR MACHINE
Choose your platform and install the Hokio connector.
Install Hokio securely from the Microsoft Store.
Install Hokio using one secure command. The installer automatically detects the device architecture and Linux environment.
curl -fsSL https://hokio.dev/download/install.sh | shWorkspace access is required to connect a device. Get launch updates when registration opens.
HOKIO + YOUR AI
Securely connect Hokio with ChatGPT, Codex, Claude, and other MCP-compatible tools.
https://mcp.hokio.top/mcpAdd the MCP URL as a remote MCP server in your AI tool, then complete the Hokio sign-in and authorization flow.
Remote MCP support and setup options depend on your tool and plan. Review the requested permissions before connecting. You can revoke access from Hokio’s connected apps settings.
Secure, read-only access. Your AI cannot change or delete your data.
A FEW GOOD QUESTIONS
Clear answers.
No infrastructure homework.
No. Your public address remains assigned to your endpoint when the connector reconnects or moves between assigned tunnel servers.
No. Keep your app running locally and connect its listening port through the Hokio connector.
Yes. Your workspace administrator can configure source IP rules, allowed HTTP methods, accepted paths, and traffic limits. Your application can also verify provider signatures.
Your URL stays assigned, but requests return an unavailable response while the connector is offline. Hokio does not queue those requests for later delivery; the sender needs to retry.
Registration is closed while we prepare for launch. Register your interest with your name and email to hear when Hokio opens. This does not create an account or reserve a webhook URL.
GETTING READY FOR LAUNCH
Registration is closed for now. Leave your name and email, and hear when Hokio is ready for your next idea.
No account to create. Just a way to stay in touch.INTEREST RECEIVED
Thanks for your interest. Your details have been submitted to the Hokio team for launch updates.
Explore how Hokio works