Plug Irish tender intelligence into your AI stack

• A tender radar for a client baseRun match across every company you look after and surface the tenders worth a look, with a one-line reason and a strong-or-possible verdict. A shortlist for a human, not an auto-decision.
• Bid or no-bid triage inside your own toolsUpload the buyer's pack, read back the requirements, the award weightings and a bid/no-bid brief, and put that verdict in front of your team before anyone commits a week to a submission.
• Drafting behind your own UIDraft answers written to where the marks are, grounded only in facts about the business, and have your own answers graded for word limits, coverage and grounding. Every draft comes back flagged for human review. Nothing here files a bid.

Create a key at Profile → API keys (workspace admins only), then confirm it before any paid call. GET /me is free, needs no scope and touches no credits.

# 1. Create a key at Profile → API keys, then confirm it (free, no credits):
curl https://tenderbuilder.ie/api/v1/me \
  -H "Authorization: Bearer tb_live_..."

# 2. Find live tenders that fit a company (3 units):
curl -X POST https://tenderbuilder.ie/api/v1/match \
  -H "Authorization: Bearer tb_live_..." \
  -H "Content-Type: application/json" \
  -d '{"description":"Dublin managed IT provider: M365, networks, cybersecurity, helpdesk."}'

For an MCP client that reads an mcpServers block, point it at the MCP endpoint through the mcp-remote bridge, which forwards your key as a header:

{
  "mcpServers": {
    "tenderbuilder": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://tenderbuilder.ie/api/v1/mcp",
        "--header", "Authorization: Bearer tb_live_..."
      ]
    }
  }
}

The full endpoint list, the workflow order, the async polling model and every error code are in the developer docs. The machine-readable spec is at /api/v1/openapi.json (no auth needed).

Two separate currencies. API units are a monthly allowance for the cheap AI endpoints, counted per workspace over the calendar month. Tender credits are the same currency the app already uses: one is consumed when a full drafting run finalises. Search and reads are free. These figures are defaults and can change, so GET /me is always the authoritative live budget.

• Bearer-key auth only, today. There is no OAuth yet, by design. Hosted connector directories that require an OAuth handshake cannot attach to it. Use a client that lets you set a static Authorization header.
• The corpus is public eTenders notices. It is a cached index refreshed by one polite daily crawl, provided with attribution for your own bidding use, never for bulk resale. Each listing carries a freshness marker and a link to the source of record.
• Nothing files a bid. There is no submission endpoint. Drafts and packs are for a person to review, edit and submit, and every draft response says so.
• We do not guess at numbers.Where a buyer's documents do not state a value, a deadline or a threshold, you get (not stated), not an estimate.

Sign up, open Profile → API keys, and mint a key with the scopes your integration needs. The free tier gives you 25 units a month to build against before you commit to a plan.