Developers · Agents
Everything machine-readable, in one place.
AI Broker publishes a Claude connector, an agent-readable index, a Markdown representation of every public page, and two embed snippets a brokerage's own site can paste. This page is the index of all of it, including the parts that do not exist yet and how to ask for them.
01·Claude connector
Ask Aoibhe from inside Claude.
The Aoibhe connector lets a broker ask their brokerage’s own AI assistant a question from Claude: on claude.ai, in Claude Desktop, in the Claude mobile apps and in Claude Code. Aoibhe answers from that brokerage’s clients, policies, cover, renewals, tasks, client conversations and regulatory calendar.
It is read only. Through the connector Aoibhe cannot change, send or delete anything: no emails go to clients, no records are edited, no tasks are closed. It is a remote MCP server over HTTPS, and you sign in with OAuth. You never paste a key into Claude.
Before you connect
- You need an Aoibhe account at a brokerage that uses AI Broker. The connector is for brokers and their staff, not for the brokerage’s clients or the public.
- Your brokerage must have the connector switched on, and your role must allow it. Owners and admins can ask for it at support@aibroker.ie.
- Two-factor sign-in must be set up on your Aoibhe account. Approving the connection asks for it.
- Any Claude plan that supports connectors. On a Team or Enterprise plan, an owner may need to add the connector for the organisation first.
Connect in Claude (web, Desktop, mobile)
- Open Aoibhe in the Claude Connectors Directory, or in Claude open Settings › Connectors and search for Aoibhe.
- Choose Connect. If Aoibhe is not listed for you, choose Add custom connector, name it Aoibhe and paste the server URL
https://api.aibroker.ie/v1/mcp. - Claude opens the Aoibhe sign-in page. Sign in, complete two-factor, pick your brokerage if you belong to more than one, and choose Approve.
- You are sent back to Claude, connected. One connection covers claude.ai, Desktop and the mobile apps.
Inside Aoibhe, Connections › Claude › Connect opens the same listing.
Connect in Claude Code
claude mcp add --transport http aoibhe https://api.aibroker.ie/v1/mcpThen run /mcp in Claude Code and sign in when the browser opens.
The tool
| Tool | What it does |
|---|---|
| ask_aoibhe | Sends the broker’s question to Aoibhe and returns her answer and a conversation_id for follow-ups. Inputs: question (required, up to 4,000 characters) and conversation_id (optional, to continue a thread). Annotated read only and not destructive. When a question is ambiguous Aoibhe asks a follow-up, sometimes with numbered options, and Claude shows it to you rather than guessing. |
Things to ask
- “Which clients renew next month and have no email on file?”
- “Which policies are due for renewal with no renewal notice sent yet?”
- “Which client conversations have gone quiet for more than a week?”
- “What regulatory deadlines are due this week?”
- “Summarise the open tasks for commercial clients.”
Security and data
- Sign-in is OAuth 2.1 with PKCE. The access token Claude holds works only on the connector endpoint. It cannot open the Aoibhe web app, its API or its file storage.
- Each call checks that your account is active, not blocked, still in the brokerage, and still allowed to use the connector. Removing or blocking a broker cuts their connection immediately.
- Claude sends only the question you ask and the thread id. The connector never reads your other Claude chats, memory or files.
- Each question and answer is saved in the brokerage’s own Ask history in Aoibhe, marked with the assistant that asked it, the same as a question asked inside Aoibhe. Data is hosted in the EU.
- Answers are generated by Aoibhe using the providers listed on Sub-processors. See the privacy notice and security.
Disconnect
In Claude: Settings › Connectors › Aoibhe › Disconnect. In Aoibhe: Connections › Claude › ⋮ › Disconnect. Admins can see and end everyone’s connections from the same menu. Either side revokes access straight away.
If something goes wrong
| Message | What to do |
|---|---|
| The Aoibhe connector is not enabled for this brokerage. | Your brokerage has not switched it on. An owner or admin can ask support@aibroker.ie. |
| Your role does not allow the Aoibhe connector. | Ask your brokerage’s admin to give your role connector access. |
| Sign-in loops or Claude says the connection failed | Disconnect in Claude, then connect again. Check that two-factor is set up on your Aoibhe account. |
| Answer ends with “truncated” | The answer was too long to return in full. Ask a narrower question. |
Support: support@aibroker.ie · Aoibhe Technologies Limited, Waterford, Ireland
02·Agent-readable files
Read the site without parsing it.
Four files describe this site to a machine. None of them need a key, and none of them are behind a crawl delay that matters.
llms.txt is the index: what the product does, who it is for, the regulatory position, and a link to every public page. It is generated per request, so a newly published article appears in it without anyone remembering to append a line. agents.md is the instruction file: when to use AI Broker, when to point the reader elsewhere, and how to fetch from us.
| URL | What it is |
|---|---|
| /llms.txt | Site index for language models. Capabilities, published writing, live production figures, contact. |
| /agents.md | Agent instructions: when to use Aoibhe, when not to, and how to call us. |
| /sitemap.xml | Every public URL, with change frequency and priority. |
| /robots.txt | Crawl policy. Search and AI assistant crawlers are allowed on everything public. |
03·Markdown
The same URL, in Markdown.
Every public page serves a Markdown representation from the same URL, negotiated on the Accept header per the acceptmarkdown.com convention. Ask for text/markdown and you get the page body without nav, scripts or layout wrappers; ask for text/html and nothing changes.
Responses carry Vary: Accept, so a CDN cannot hand an agent’s Markdown to a browser or the reverse. A client that accepts neither representation gets an honest refusal rather than a silent fallback: HTTP 406, listing what is available. A path that does not exist returns a real 404 with a Markdown body pointing at the site map.
If your client does not negotiate on Accept, append .md to any path instead. The home page is /index.md.
curl -s -H "Accept: text/markdown" https://www.aibroker.ie/features/radar
curl -s https://www.aibroker.ie/features/radar.md
curl -sI -H "Accept: text/markdown" https://www.aibroker.ie/security | grep -i -E "content-type|vary"Markdown responses are edge-cached for five minutes and carry the page title, description and canonical URL as YAML front matter.
04·Embed
Put Aoibhe on your own site.
The chat widget is one script tag. It takes your tenant slug and a publishable embed key, both issued from your Aoibhe settings, and mounts a launcher that talks to your brokerage’s own configuration. An embed key is scoped to an explicit list of origins (an empty list denies every request rather than allowing all of them) and it can be revoked, so a key scraped off your page is a key you turn off.
The script served at /embed.js is a loader: it injects the SDK bundle and forwards the data attributes. Point data-ai-broker-base-url at a different host only if you are testing against a non-production deployment.
<script src="https://www.aibroker.ie/embed.js"
data-ai-broker-tenant="YOUR_TENANT_SLUG"
data-ai-broker-embed-key="YOUR_EMBED_KEY"
async></script>05·Forms
A proposal form, embedded.
Any form built in Aoibhe can be hosted by us on a white-label page and shared by link or QR code, or embedded into your own page with a second snippet. Replies fold back into the same conversation as the rest of the client’s thread, so an embedded form is not a separate inbox to check.
The embed takes the form’s public id and the same embed key as the widget.
<div
data-aoibhe-form="FORM_PUBLIC_ID"
data-aoibhe-embed-key="YOUR_EMBED_KEY"
></div>
<script src="https://www.aibroker.ie/embed-form.js" async></script>06·API access
What we have not published.
There is no public REST API and no OpenAPI specification today. The API behind the product authenticates per brokerage and is not offered to third parties, and publishing a spec for endpoints nobody outside the product can call would be marketing rather than documentation.
The Claude connector above is the one programmatic surface we offer, and it is read only. If you are integrating a brokerage’s own systems and need more (a book export, a webhook on a task, a write path from your own software), write to support@aibroker.ie with the shape of the integration and we will tell you honestly whether it exists, is planned, or is not something we will build.