Now / Next
This page is a snapshot, not a changelog. We refresh it as the product moves — usually about once a week — so you see where Caib stands today and what we refuse to treat as “finished”, without a diary of every past release.
Now
If you’re a supplier trying to stay visible and accurate when people ask AI tools about you, Caib is already the place where your offer can live as structured, honest facts — stock, services, slots, jobs, and the messy reality of “do you have it / when?” — instead of leaving that to a noisy website and hoping the model guesses right.
Behind the scenes runs the Registry: a hosted catalogue your team (or your agency) can publish into, with verification when you want “right now” to mean today, not last month’s crawl. Operators use user.caib.io; buyers and curious machines meet you on registry.caib.io and verify.caib.io without you having to become an API expert on day one.
Geocoding is part of that same promise of facts, not vibes: important listings can carry real premises — address and place the catalogue can reason about — so when someone asks “where are they?” or “what’s near me?”, an assistant has something solid to cite instead of inferring geography from a noisy site footer. For suppliers that means fewer wrong-place disappointments; for AI systems it means one less guess in a chain that was never meant to be a geography quiz.
Caib now also gives agents a controlled way to ask a human. If an AI system has a question the Registry cannot honestly answer — a special availability check, a pricing edge case, a human judgement call — it can submit an AI-to-human enquiry for the selected tenant and provide a response email or URL. The benefit for the user is control: enquiries land in Caib, and the tenant can turn the channel off at once. The benefit for the AI is clarity: instead of guessing or scraping a contact page, it receives an immediate “accepted” or “not accepting enquiries” response.
Users can also add Caib-powered forms to their own website or domain. A normal human enquiry form can send visitor messages straight into the Caib Forms inbox, while an AI-to-human form can route agent questions through the Registry contract. In both cases, the tenant keeps the responses in one place inside Caib rather than scattering them across inboxes, plugins, and site builders.
We also operate an MCP server (Model Context Protocol). That is the same idea as plugging Claude, Cursor, and other MCP-aware tools into a small set of well-named actions — search the public catalogue, fetch a listing, and (where your team has wired authentication) queue a draft for review the same way the operator site does. The benefit is simple: assistants and automation stay on the same structured data as the Registry API, not a one-off scrape of a marketing page. MCP overview.
What you get today: a credible path from “we exist on the web” to “assistants can quote us without inventing us” — with onboarding that uses our own AI to guide you, forms that capture human demand directly into Caib, and a human escalation path when an assistant needs an answer only an operator can give.
Next
What comes after “working product” is not a single milestone — it is discipline. Caib is committed, over the long haul, to best-in-class GEO for the Registry: generative-engine optimisation in the true sense — the patient work of structure, clarity, freshness, authority, and crawlability so that assistants and AI-first search treat the catalogue as a source worth citing, not a page to scrape when nothing better exists.
The principle is spare. If the Registry wins at GEO, our clients inherit the traffic. They gain a fairer shot at being found and quoted correctly when buyers ask machines first — without running a parallel science project on every AI and website. In that world, suppliers can let Caib carry the AI-discovery burden and return their attention to humans: the conversation, the visit, the quote, the relationship — the places where software still only assists.
If you’re comparing or selling Caib
Agencies: you can point clients here weekly — it’s the honest state of play. Technical partners: the contract remains openapi.json; this page is deliberately human.