One signup.
Two ways to integrate.

1. Discover the current state

Demo manifest · Signup OpenAPI · Data-query schema · Product catalog · Text overview

GET https://www.dajotaappfactory.com/signup.php reports whether invitation intake is accepting requests. It is separate from data API availability. Do not infer a running MCP server from a planned URL.

2. Submit your invitation request

Send JSON to POST https://www.dajotaappfactory.com/signup.php, with Content-Type: application/json and Accept: application/json. Use contact details you are authorized to provide. The optional request ID must be 16–64 letters, digits, underscores or hyphens; reusing it with the exact same body returns the original receipt. Changed details require a new request ID.

{
  "requestId": "replace-with-your-unique-request-id",
  "name": "Your agent or team",
  "email": "operator@example.org",
  "visitorType": "agent",
  "useCase": "Evaluate dependency checks in our coding workflow.",
  "privacyAcknowledged": true
}

HTTP 202 with status: pending-local-save means the request is encrypted and queued on our website, not yet confirmed in our local database. Preserve the receipt securely. It does not establish email ownership or active access. A local worker normally collects requests every 30 seconds while online. Receipt status saved-locally confirms the database save. Unconfirmed encrypted payloads expire after seven days (handoff-expired); receipts and locally saved requests expire after 90 days. An outage may delay pickup. A later public account is a separate workflow. Only service-related follow-up is requested, not marketing enrollment.

3. Check the receipt without leaking it in a URL

POST to the same endpoint with the same JSON headers:

{"action":"status","receipt":"YOUR_PRIVATE_48_CHARACTER_RECEIPT"}

The response contains status, savedLocally, savedLocallyAt, receivedAt, queueExpiresAt and expiresAt, not contact details or a credential. Unknown or expired receipts return 404. Checks are rate-limited; do not poll frequently.

4. Activate an approved invitation

After contact verification and individual approval, the operator receives a one-use invitation valid for 24 hours. Humans can paste it into the secure API activation page. Agents can send POST /v1/demo/activate to the separately verified HTTPS API origin with this JSON body:

{"invitation":"YOUR_PRIVATE_INVITATION","termsVersion":"free-trial-20260916-v1","acceptTerms":true}

Set acceptTerms only with your operator’s authorization to accept the free-trial terms. A successful response returns an API key once. Store it privately; never print it into agent traces. Do not follow redirects or retry activation automatically. If delivery is interrupted, request a replacement invitation. Replacing a key preserves the account’s existing allowance. Trial access ends October 16 at 00:00 Eastern (04:00 UTC).

Use REST or MCP after activation

The free data routes at https://api.dajotaappfactory.com are POST /v1/demo/security/query and GET /v1/demo/usage. MCP at https://api.dajotaappfactory.com/mcp provides demo_security_query and demo_usage. They share a daily account allowance: 100 queries or 10 MB of JSON data. At most five package/version inputs, ten admitted attempts per minute, candidate limit 1–50 and offset 0–5000.

Wait for an invitation containing the verified HTTPS endpoint and credential-delivery instructions. Keep keys in a protected credential store and transport headers, never tool arguments, URLs or signup forms. No payment authorization is needed for demo queries. Inspect MCP structured status even when HTTP is 200; inspect source timestamps, public coverage notices, unknown matches and hasMoreCandidates.

5. Planned paid credits and spending authority

Purchase prepaid ADX usage credits through Stripe, starting at $10. Each request deducts its quoted price from your balance; your card is charged when you purchase credits, not for every lookup. At the planned $0.01 security-query price, $10 provides 1,000 requests. Larger credit purchases will be available. Paid access is not open yet.

An authorized operator would fund credits and explicitly grant spending authority to the agent. Agents would consume that balance within the operator’s limits; signup does not establish payment authorization. Do not infer permission to fund, refill or spend from an invitation receipt.

Manual top-ups will start at $10. Optional automatic refill is planned and requires explicit customer consent, a disclosed trigger and refill amount, and spending limits. Every purchase or refill must meet the $10 minimum. It is not enabled by signup or demo use.

Batched x402 settlement for wallet-paying agents is an option under evaluation, not an implemented or available payment method. Funding endpoints, balance APIs and payment examples are not available. Keep using the free-demo invitation process; do not send payment credentials here.