Developers

Build on the hellojade platform.

Everything a developer — or the coding agent working for one — needs to integrate with hellojade: the Partner Intake API, the public plan feed, the OpenAPI spec, the integration brief, and ten client kits.

Provide leads Guide for coding agents

Documentation

Two pages, written to be read once.

One for the integration itself, one for the agent that will write it.

Provide leads — Partner Intake API

Send leads to a hellojade customer: one POST, an API key, an idempotency key, a 202 that means committed to disk.

For coding agents

What an AI coding agent needs to build against each public API — live sources, auth, limits, idempotency, done criteria.

Machine-readable

Generate from the source, not from a copy.

These are served by the platform and change without a deploy on your side. Fetch them at build time or at run time; do not vendor them.

OpenAPI 3.0 specificationmachine-readable

The machine-readable contract for the Partner Intake API. Generate your types from it rather than hand-writing them.

Integration brief (INTEGRATION.md)machine-readable

The brief a partner reads once, front to back: the key check, the eight rules, the envelope, responses, limits and the definition of done.

Project vocabulary (live)machine-readable

The controlled project_area / project_service values, read from the same table the validator reads. Fetch it; never hard-code it.

Subscription plan feedmachine-readable

The public JSON feed of published subscription plans — read-only, no key.

The Partner Intake API also has a browser playground that runs the server's real validator: intake.hellojade.ai/api.

SDKs

One contract, ten kits.

Each repository wraps the same one-call contract: check the key, post a lead with an idempotency key, retry only on 5xx and 429. Read the language's README for install and the brief for the rules.

leads-goGo

Go client for the Partner Intake API. Module path github.com/hellojade-ai/leads-go.

leads-cliGo

Command-line client: check a key, post a lead, read the vocabulary.

leads-rustRust

Rust client for the Partner Intake API.

leads-nodeJavaScript

Node.js / TypeScript client for the Partner Intake API.

leads-jsJavaScript

Browser and edge-runtime JavaScript client.

leads-pythonPython

Python client for the Partner Intake API.

leads-rubyRuby

Ruby client for the Partner Intake API.

leads-phpPHP

PHP client for the Partner Intake API.

leads-javaJava

Java client for the Partner Intake API.

leads-dotnetC#

.NET (C#) client for the Partner Intake API.

The kits are named leads-<language> under github.com/hellojade-ai — leads for the service, because later services get their own kits. All ten are published. The API itself needs no SDK — the whole integration is one HTTPS POST.

Start here

Prove your key before you write code.

The endpoint authenticates before it validates, so an empty body with a real key answers 422 — proof the key works — and nothing is stored, delivered or emailed.

curl

curl -i -X POST https://intake.hellojade.ai/v1/intake \
  -H "X-API-Key: $HELLOJADE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{}'
# 422 validation_failed  → the key is valid; nothing was stored
# 401 unauthorized       → the key is missing, mistyped or revoked

Need a key? Keys are issued per lead source by the hellojade customer you are sending to. Contact us and name the customer and the feed.

Build on the hellojade platform.

Two pages, written to be read once.

Generate from the source, not from a copy.

One contract, ten kits.

Prove your key before you write code.

Building something that needs a key?