Phase 26 · Global Evidence Infrastructure

Build on inspectable health evidence

The developer kit exposes public, non-personal evidence reads. It does not certify integrations, grant clinical approval, or claim that any external organization has adopted these contracts.

Discover the contracts

Authenticated private decisions

The portable ./private export supports ephemeral context tokens and categorical composition. It sends caller-supplied health context only in authenticated JSON POST bodies. It is not a durable profile, clinical approval, or individual outcome prediction.

import { EvidenceBasedPrivateClient } from './dist/developer-kit/private.mjs';

const privateApi = new EvidenceBasedPrivateClient();
const context = await privateApi.createContext(
  { context: { medications: ['warfarin'] }, ttl_seconds: 300 },
  process.env.EVIDENCEBASED_CONTEXT_TOKEN
);
const decision = await privateApi.compose(
  { query: 'magnesium for sleep', contextToken: context.context_token },
  process.env.EVIDENCEBASED_COMPOSE_TOKEN
);

Tokens must be server-side secrets. Never place health context or capability tokens in URLs, browser tracking systems, logs, or public audit records.

Try the public API now

No account, package, or repository checkout is required.

curl --fail-with-body --silent --show-error \
  'https://evidencebased.info/api/v1/aeo/claims?intervention=mg'

The response includes dataSource, count, and a claims array. An empty array is a valid result; never assume claims[0] exists.

# Exact immutable claim version
curl --fail-with-body --silent --show-error \
  'https://evidencebased.info/api/v1/aeo/claims/clm_legacy?version=0'

# Resume a list using page.nextCursor from the prior response
curl --fail-with-body --silent --show-error \
  'https://evidencebased.info/api/v1/aeo/claims?limit=25&cursor=OPAQUE_NEXT_CURSOR'

page.snapshotId binds the ordered page and cursor, while dataset.snapshotId binds the canonical dataset. Treat cursors as opaque and restart pagination if the API reports a stale or invalid cursor. Preserve dataSource: fallback as unverified rather than silently presenting it as live evidence.

Dependency-free TypeScript client

The repository client covers public evidence, safety, product, standards, globalization, observational aggregates, and roadmap readiness. It throws on HTTP and non-JSON failures rather than returning a plausible empty answer.

// First run: npm run developer-kit:build
import { EvidenceBasedClient } from './dist/developer-kit/client.mjs';

const evidence = new EvidenceBasedClient();
const { claims, dataSource } = await evidence.listClaims({ intervention: 'magnesium' });

// Keep the live/fallback label and evidence certainty visible.
console.log(dataSource, claims[0]?.certainty);

Typed failures

import { EvidenceBasedApiError } from './dist/developer-kit/client.mjs';

try {
  await evidence.getClaim('clm_legacy', { version: 999 });
} catch (error) {
  if (error instanceof EvidenceBasedApiError) {
    console.error(error.code, error.status, error.requestId);
  }
}

Distribution: repository-portable-build. Build with npm run developer-kit:build. No npm publication or external adoption is claimed.

Validate locally

npm run standards:validate -- claim examples/developer-kit-claim.synthetic.json 1.0.0

Verify all public integration invariants with npm run developer-kit:verify -- https://evidencebased.info.

The verifier checks that legacy-unverified claims are exposed with honest governanceMode and governanceStatus fields; it does not certify them as governance-verified.

The validator runs on the integrator’s machine and transmits no record. Schema validity does not establish scientific truth, review, publication eligibility, safety, certification, regulatory approval, laboratory testing, external adoption, or reuse permission.

Integration invariants

Preserve dataSource, certainty, safety qualifiers, provenance, versions, and limitations.
Never convert fallback data, observational outcomes, or schema validity into clinical approval.
Never merge evidence certainty, interaction severity, product quality, value, or personal applicability into one score.
Do not send personal health information to public read endpoints or the offline validator.
Use roadmap readiness for exact inventory and gaps; never convert its conservative proxies into scientific completeness.
Support is best-effort with no SLA. The API and kit are evidence infrastructure, not medical advice, diagnosis, treatment, or authorization for clinical use.