Agoo is in early access
Run your front door. Build on it too.
Guides for every role at the door, and everything developers need to connect Agoo to the systems you already run.
Use Agoo
Guides
Set up your organisation, pair kiosks, invite visitors, take bookings and run attendance, step by step.
All guidesBuild with Agoo
Developers
Connect Agoo to your systems with the REST API and webhooks, or let AI assistants work with it through MCP.
All developersStart from your role
Owners and adminsSites, people, branding, forms, billing.Front desk and guardsCheck-in, passes, deliveries, the register.HostsApprove arrivals and invite guests.EmployeesClock in and out, request leave.Security and facilitiesWatchlists, roll call, audit trail.DevelopersAPI, webhooks, SDKs and plugins.
Developer platform
One contract, many ways in.
The REST API is the source of truth. Webhooks, the SDKs, the CLI, the WordPress plugin and the MCP server are all built on it, so they share the same permissions, audit trail and rate limits.
# Who is on site right now?
curl https://api.agoo.ardent.africa/v1/visits?status=checked_in \
-H "Authorization: Bearer $AGOO_API_KEY"PreviewREST APIVisits, invitations, people, bookings and attendance over JSON.PreviewWebhooksSigned events the moment someone arrives, books or clocks in.PlannedMCP serverLet Claude, ChatGPT and Cursor ask Agoo questions, with your permissions.PlannedTypeScript SDKTyped client for Node, Bun, Deno and Workers.PlannedWordPress pluginBooking pages and pre-registration on your WordPress site.PlannedAgoo CLIForward webhooks to localhost, import people, script your setup.
Agoo MCP server
Ask your front door, from the assistant you already use.
Connect Agoo to Claude, ChatGPT, Cursor or VS Code. Ask who is on site, find a free slot, invite a guest or check who hasn't clocked in. Every call runs with your own permissions and lands in the audit trail.
How the MCP server works