Is this export in the npm package's published type declarations

$0.005 USDC per call · Developer and security · POST /api/v1/symbol-exists · Id symbol-exists

Checks that up to 20 named exports (functions, classes, constants, types, default) exist in the .d.ts files published for an exact npm package version, read from jsDelivr, for coding agents that may be calling an API that does not exist. Follows export lists and relative export-star re-exports within the package (at most 7 files) and reports when the export surface cannot be fully enumerated. Never downloads or runs the package code; packages typed only through @types or without declarations return unsupported; does not check signatures or arguments.

What you get

Catches hallucinated API names before the build or the reviewer does.

Call it

Send the JSON body below to https://agents.writerslogic.com/api/v1/symbol-exists. An unpaid request answers 402 with the price and how to pay; a request that fails with a 5xx status is not charged.

curl -i -X POST https://agents.writerslogic.com/api/v1/symbol-exists \
  -H 'content-type: application/json' \
  -d '{"package":"nanoid","version":"5.0.7","symbols":["nanoid","customAlphabet","nonexistentFn"]}'

Input

FieldTypeRequiredDescription
packagestring; length 0..214yesnpm package name.
versionstring; length 0..64yesExact version or dist-tag (jsDelivr resolves it).
symbolsarray<string; length 0..100>; max 20 itemsyes
entrystring; length 0..100nopackage.json exports key, default '.'.
typesPathstring; length 0..200noDeclaration file path inside the package, overriding package.json resolution.

Example request body

{
  "package": "nanoid",
  "version": "5.0.7",
  "symbols": [
    "nanoid",
    "customAlphabet",
    "nonexistentFn"
  ]
}

Result

The response is { "data": ..., "_provenance": ... }. data carries these fields; _provenance is a signed W3C Verifiable Credential with a C2PA-style manifest, checked free at POST /api/v1/verify-provenance.

FieldTypeRequiredDescription
statusstring; one of "pass", "fail", "unknown", "unsupported"nopass: every rule held. fail: a rule was violated (see witnesses). unknown: the input lacks the evidence to decide. unsupported: outside what this engine covers. Missing evidence is never a pass.
packagestringno
versionstringno
completebooleannoTrue when the whole export surface was enumerated, so a missing symbol is a real absence.
filesReadarray<string>no
incompletearray<string>no
symbolsarray<object>no
witnessesarray<object>no
versionsobjectnoEvery semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile).
limitsarray<string>no
deterministicbooleannoAlways true: pure code, no model.

Pay and connect

Available through: x402 (USDC on Base), MCP. MCP clients reach it through the code-preflight-kit package.

Machine-readable