Agent-native infrastructure

Know before your agent installs.

Dependency Preflight checks exact npm and PyPI package versions before installation and returns a deterministic ALLOW, REVIEW, or BLOCK decision with reasons and source evidence.

View free demo Read API docs

$0.02 USDC / live request No subscription No persistent customer account

Preflight decision flow agent-ready

Agent requests dependency

npm · example-package@1.0.0

Dependency Preflight

exact version → evidence → policy decision

ALLOW

REVIEW

BLOCK

Made for narrow, composable agent workflows

npm PyPI REST / JSON USDC / request

Simple by design

A small decision point before installation.

Put a machine-readable checkpoint between an agent choosing a dependency and actually installing it.

Request

Your agent submits one or more exact npm or PyPI package versions for a preflight check.

Evaluate

Dependency Preflight checks package metadata and evidence, then applies a defined policy.

Decide

Your automation receives ALLOW, REVIEW, or BLOCK and can continue, escalate, or stop.

Why preflight?

Give autonomous installs a checkpoint.

The goal is not another dashboard. It is a compact decision service that agents can call exactly when they need it.

Check the exact version

Evaluate the package version the agent is actually about to install, rather than relying on a vague package-level signal.

Return a deterministic category

Translate evidence into a compact ALLOW, REVIEW, or BLOCK result that automation can handle predictably.

Keep evidence attached

Return the reasons and source evidence behind the result so the next agent or human can inspect what drove the decision.

Escalate instead of guessing

Use REVIEW as a deliberate pause point when a dependency deserves human or higher-level agent attention.

First service

Dependency Preflight

Known-vulnerability, release-age, install-script, lifecycle, license, and package-metadata checks for exact npm and PyPI versions.

Built for automation, not accounts.

The service stays intentionally narrow: structured input, structured output, and pay-per-use access when your workflow needs it.

Evaluate up to ten exact package versions per request
npm and PyPI ecosystems
ALLOW / REVIEW / BLOCK at package and request level
Source evidence and findings included in JSON
No subscription or persistent customer account

POST /v1/dependency-preflight
Content-Type: application/json

{
  "ecosystem": "npm",
  "packages": [
    {
      "name": "example-package",
      "version": "1.0.0"
    }
  ],
  "policy": "balanced"
}

{
  "request_id": "req_…",
  "decision": "allow",
  "policy": {
    "name": "balanced",
    "version": "…"
  },
  "summary": {
    "package_count": 1,
    "allow": 1,
    "review": 0,
    "block": 0
  },
  "packages": [
    {
      "name": "example-package",
      "requested_version": "1.0.0",
      "decision": "allow",
      "findings": [],
      "evidence": [ ... ]
    }
  ]
}

Abbreviated from the current public API shape. See the OpenAPI specification for the complete authoritative schema.

Free fixed demo

See the response shape without paying.

The demo returns a fixed example so visitors can inspect the decision structure before making a live request.

View raw JSON

ALLOW

Packageexample-package@1.0.0

LicenseMIT · allow

DeprecatedNo

Vulnerabilities0 in fixed demo

Findings0 in fixed demo

PartialNo

Pay per use

$0.02 USDC / live preflight request

No recurring plan. Call the service when an agent needs a decision, pay for that request, and move on.

Free fixed demo No subscription No persistent customer account

Preflight Stack

One focused service first. More later.

Preflight Stack is an umbrella for small, agent-native API services. Dependency Preflight is the first.

First service

Dependency Preflight

Exact npm and PyPI version checks with deterministic decisions, findings, and source evidence.

Future

More focused checks

Additional services can be added when a narrow, reusable decision point is genuinely useful to agent workflows.

Design principle

Small, composable APIs

Keep services machine-readable, easy to inspect, and callable only when the workflow needs them.

FAQ

Short answers for builders.

What does Dependency Preflight check?

It evaluates exact npm or PyPI versions using package metadata and evidence including lifecycle information, known-vulnerability data, install-script signals, and license-related policy inputs.

What happens when the result is REVIEW?

REVIEW is a deliberate escalation signal. Your workflow can pause, route the evidence to a human or another agent, or apply whatever review policy you choose before installation continues.

Do I need an account or subscription?

No subscription is required, and the service is designed without a persistent customer account requirement. Live preflight requests are pay-per-use.

Is the free demo a live dependency lookup?

No. The free demo is intentionally fixed so anyone can inspect the response structure without payment. Live dependency checks use the preflight endpoint.

How much does a live request cost?

A live Dependency Preflight request costs $0.02 USDC. The fixed demo remains free.