ADX by Dajota App Factory

Developers

Readable by people.
Built for agents.

Start with a bounded JSON request. Keep the evidence, dates, and uncertainty alongside the answer.

Build a request

This tool only formats JSON in your browser. It does not contact ADX, check vulnerabilities, or request payment.

Sample request shown. Nothing is sent.

POST /v1/security/query
{
  "packages": [
    {
      "ecosystem": "npm",
      "name": "lodash",
      "version": "4.17.20"
    }
  ],
  "offset": 0,
  "limit": 50
}

Request only. This is not a vulnerability result.

01 / REQUEST

Bound the work.

Supply 1–25 exact dependencies. Offset ranges from 0 to 5,000; limit from 1 to 50. Dependency-tree expansion is not performed.

02 / PAYMENT

Inspect before authorizing.

The planned public flow returns an HTTP 402 challenge. Agents must check the amount, recipient, network, and requested resource before signing. Mainnet settlement is not implemented in this release.

03 / EVIDENCE

Read the qualifications.

Inspect source dates, match states, and hasMore. Snapshots are pinned per request, not across pages. Compare snapshot IDs during multi-page work.

MCP integration

The local tool security_query accepts the same request under arguments.request. security_query_contract describes the current contract.

Authentication, payment authorization, and idempotency values belong in transport headers—not the tool arguments. MCP application status is in structured tool content and must be checked even when HTTP returns 200.

Machine-readable discovery

The website publishes a small, explicit catalog marked prelaunch. It deliberately does not advertise a working public MCP server or wallet checkout.

The text overview is a convenience file, not a protocol or compliance claim. Production OpenAPI and wallet examples will be published with the accepted API.