Design partners

Build on it while it is still small.

We are looking for ten AI products to integrate the registry now, while it is early enough that what you need still changes what we build.

Read this part first

The endpoint is correct. The records underneath it are thin.

Measured 2 August 2026: across our entire base, 39 people carry the two or more beats that is_human requires, and four of five real consented records answered all-nulls. If you integrate today and query your own users, most of them will not be in the registry at all, and the ones who are will mostly return null.

We are telling you this on the pitch page rather than after you wire it up, because the version of this product worth paying for is the one where your users have accrued a record, and that takes weeks of them showing up. A design partner who expects working answers on day one will be disappointed, and correctly so.

What is real today: the API, the consent rail, the revocation, the evidence in every response, and the guarantee that a claim we cannot evidence comes back null rather than false.

What you get

Free, uncapped

No metering, no ceiling, for the whole partnership. The published price is free through 1,000 active records a month and five cents after; you pay neither.

The founder, directly

One person built this estate. You get him on email, not a support queue and not a bot.

Shape the API

Claims, thresholds and response shape are still moving. What you need is what gets built next.

Price locked

Whatever the registry costs later, your rate is the one we agree at the start, in writing.

What we need from you

  1. A real integration, in something people actually use. Not a prototype in a branch.
  2. The truth when it is bad. Tell us when a claim was useless, when the latency hurt, when the null rule got in your way. That is the entire point of the arrangement.
  3. Your users stay yours. We never contact them, never market to them, and never see anything they wrote. We only ever answer four questions about the ones who granted you.

The whole integration, over REST

curl -H "Authorization: Bearer noctara_lk_your_key" \ https://noctaracorp.com/api/v1/registry?tag=your_client_tag { "claims": { "is_human": true, "is_continuous": true, "has_deviated": false, "stands_behind": true }, "provenance": { "beats": 14, "distinct_weeks": 6, "thresholds": { "is_human": ">= 2 beats" } }, "consent": { "granted": true, "revocable_at": "/consent" } }

Or over MCP, if your client speaks it

The tool is pupul_registry on our hosted server. It carries an output schema, so a model gets structured results rather than prose it has to parse.

{ "mcpServers": { "noctara": { "type": "http", "url": "https://mcp.noctaracorp.com/mcp", "headers": { "Authorization": "Bearer noctara_lk_your_key" } } } }

The tool description tells the model outright that null means unestablished and must not be reported as a negative finding. We would rather constrain the model than trust it to be careful with someone's personhood.

Mint a key before you talk to us

You do not need our permission to start. Credentials are self-serve and instant, and the free tier is real, so you can evaluate the whole thing before deciding whether the partnership is worth your time.

curl -X POST https://noctaracorp.com/api/partner-signup \ -d '{"company":"Your Company","email":"you@yourcompany.com"}'
Email the founder

Tell us what you are building and what you would need the registry to answer. That is the whole application.

Prices and honest scope: for builders  ·  Full reference: integration docs  ·  What a person sees and can revoke: their own record.