VERAHELMAPI / V1CUSTOMER ACCESS ↗

VERAHELM API / AI CHANGE GATES

Gate an exact AI change with bounded evidence.

Use one API contract to evaluate a pull request, migration, agent, MCP server, model, or workflow version. Thirteen gate profiles return deterministic status codes, blocking conditions, required tests, provenance, and optional signed Decision Envelopes. Customer payloads and full outputs are not persistently retained.

GET API ACCESS →PR GATE QUICKSTART ↗ALL GATE PROFILES ↗CREATE A FREE KEY ↗
BOUNDED AUTHORIZATION RECORD. A gate result or Decision Envelope is not certification, a safety finding, professional advice, compliance approval, or production authorization. Customer authority and independent controls remain required.

01 / FLAGSHIP WORKFLOW

Gate an exact pull-request or agent change.

PRIMARY

PR and agent change

Bind a bounded result to the exact subject and version, then verify the signed lifecycle record independently.

SECONDARY

Tool admission

Record a bounded customer decision for a specific integration and revisit it when scope or version changes.

SECONDARY

Migration readiness

Preserve customer-selected evidence references, conditions, expiry, and retest requirements.

LIFECYCLE

Retest and failure coverage

Keep expired, revoked, superseded, and unresolved states visible without publishing private decision logic.

02 / DIFFERENTIATED VALUE

An authorization record—not another content warehouse.

Evaluation, observability, security, governance, and policy tools produce or retain evidence. Verahelm addresses a narrower job: bind bounded, caller-supplied evidence references and customer authority to an exact change and a verifiable lifecycle record.

BOUNDARYVERAHELM
Primary jobEvidence-to-change-gate decision support for an exact subject and version
Required dataBounded structured summaries; raw repositories, prompts, traces, and datasets are not required
OutputStructured result with an optional signed Decision Envelope
LifecycleExpiry, revocation, and supersession
VerificationOffline public-contract verification

Provider capabilities vary by product and plan. Verahelm complements evidence-producing systems and does not independently verify caller-supplied evidence.

03 / ACCESS PRODUCTS

Revocable entitlements with hard limits—never permanent keys.

SELF-SERVICE / NON-PRODUCTION

Free access

$0

30 units each calendar month—about ten base three-unit gates. One restricted key, selected flagship endpoints, low rate/concurrency, non-production marker, recorded purpose, and immediate revocation. Stripe payment-method verification is required; no charge or subscription is created.

SELF-SERVICE

Developer access

$49/month
PURCHASE →

300 units per billing period; 30 units/day; 5 requests/10 seconds; 30/minute; concurrency 2; one live key; 12,288-byte payload; 6-second processing limit.

At the base request size, 300 units cover up to 100 three-unit PR or agent-change gates per billing period, subject to daily and rate caps.

SELF-SERVICE

Professional access

$149/month
PURCHASE →

1,500 units per billing period; 150 units/day; 13 requests/10 seconds; 90/minute; concurrency 5; five live keys; 16,384-byte payload; 8-second processing limit; metadata-only usage export.

At the base request size, 1,500 units cover up to 500 three-unit gates. Five keys support separated integration scopes, while metadata export supports internal usage reconciliation.

UNIT POLICY. Unused units expire at billing-period end; no rollover, automatic overage, or surprise billing. Support is email best effort with no response-time SLA. Daily and monthly limits are hard.
BUSINESS ACCESS. Negotiated limits, multiple authorized contacts, optional IP restrictions or mTLS, custom data terms, manual engagements, and VH Register are sales-assisted under a separate signed agreement. No self-service team administration is included.

04 / DATA + OUTPUT

Minimal retained data. Bounded results.

NO PAYLOAD HISTORY

Request-content boundary

  • No raw inputs or outputs in persistent databases, caches, queues, analytics, or logs
  • No saved prompts, runs, evidence, uploads, URLs, web crawling, or background content jobs
  • Only billing, usage, consent, security, and operational metadata retained
BOUNDED OUTPUT

Documented contracts

  • Strict public schemas and closed result codes
  • Caller-supplied evidence is not represented as independently verified
  • Responses remain preliminary and scope-bound
  • Unsupported context returns a manual-review recommendation

05 / INPUT RESTRICTIONS

Small JSON summaries—not customer datasets.

ACCEPTEDREJECTED
Short descriptions, enumerated categories, bounded integer metrics, categorical observations, small arrays, non-identifying labels, and non-confidential customer summaries.Multipart, binary, base64 files, attachments, archives, executables, remote URLs, cloud links, repository links, webhooks with payloads, streaming inputs, bulk data, HTML, and source code.
United States business/professional, age 18+, authorized, non-regulated and non-consequential internal evaluation support.Personal or regulated data, credentials, card/bank data, confidential files, third-party trade secrets, high-consequence decisions, certification, advice, weapons, surveillance, or critical controls.
PROHIBITED DATA + USES ↗ACCEPTABLE USE ↗

START SMALL

Run a bounded non-production gate.

Verify a payment method without a charge, create a restricted Free key, and inspect one bounded result. Upgrade only if the workflow earns it.

CREATE FREE KEY ↗READ THE DOCS ↗