For software vendors

Your customers already ask Grok.

And Claude. And ChatGPT. Their staff paste job numbers and customer names into a chat window today — an integration with no auth, no scope and no log. The official connector, under your name, is how it becomes yours.

01 — What you're actually buying

Not a chatbot. A trust boundary.

Your customers' staff have already invented the integration. The connector is the same thing — except this one has a scope, a log and an off switch.

Don't be the login page.

Connectors are being built around vendors right now — by customers' own developers, by third parties, by us. The official one carries your name in the directories Grok, Claude and ChatGPT already search. That slot is worth holding.

Security you can show.

Read-only defaults, writes behind explicit named scopes, no end-user credentials held, scrubbed logs, and a published security note with every release. Built to pass your customers' audits — and yours.

Money that makes sense.

A service, not a hire. Build, hosting, monitoring and an upkeep SLA on one retainer — no headcount, no roadmap diversion. Your engineers keep shipping your product.

Risk that's managed.

APIs drift and connectors rot. A field rename kills a homemade script on a Friday night; the retainer is what catches it first. Quarterly depth releases, not a repository that stops merging.

02 — What you sign

Under your name. On your authority.

The connectorOfficial, designed to your API's scopes, published under your name.
Directory listingsSubmitted on your authority — you approve every surface it appears on.
Hosting & monitoringRun and watched by us; incidents reported to you, not discovered by your customers.
The retainerUpkeep SLA — because the work never finishes. Your roadmap stays yours.
hello@hardlink.com.au

One email. We'll bring the scoped design, you bring the API docs.