---
title: "Buy Latitude 10 Agentify API for Node.js"
method: GET
path: "/api/agent-products/agentify-api"
tags: ["Developer kits"]
---

# Buy Latitude 10 Agentify API for Node.js

`GET /api/agent-products/agentify-api`

## Request

- Base URL: `https://latitude10.tech`
- URL: `https://latitude10.tech/api/agent-products/agentify-api`
- Auth: none required

For Node.js (Express, Hono, Fastify, Next.js): make the API you already have agent-ready, in the same process: a middleware for Express 4 and 5, Hono, Next.js and Fastify, and a CLI. It reads your OpenAPI spec (or drafts one from your routes without running your code) and mounts an MCP endpoint (MCP 2026-07-28 and 2025-xx) with one tool per operation, reads on and writes off by default. A tool call runs in-process through your own route handlers, so your auth, validation and logic apply. Discovery from the same spec: /llms.txt and /llms-full.txt, the MCP server card (SEP-2127 draft) and AI Catalog, /openapi.json with agent hints, OAuth protected-resource metadata, /.well-known/x402 and an /agent index. Agents authenticate with your API’s own credentials, agent keys, or OAuth, including Amazon Cognito machine-to-machine tokens (how AWS AgentCore Gateway calls a target). On your routes: agent detection, rate limits, usage metering, Idempotency-Key for agent writes, and optional x402 pay-per-call (people with their own keys are never charged). An agent-readiness check scores your spec 0 to 100 and agentify improve fixes it. Memory, SQLite or Postgres. Includes a setup wizard (node setup.mjs) that makes a bundled Orders API agent-ready in the framework you pick.

## Response `200`

Paid: the product (for a kit, a personal download link for the zip) and the payment.

- object
  - `product` object, required
    - `slug` 'agentify-api', required
    - `name` string, required
    - `version` string, required
    - `description` string, required
    - `delivery` 'kit', required
    - `content` string, nullable, required: Personal download link for the zip (latest release). Valid 24 hours; each purchase allows 10 downloads. Null only if the link could not be created; see support.
    - `contentExpiresAt` string, nullable, required: When content stops working (ISO 8601).
    - `support` string: Present only if something failed after payment: email jorge@latitude10.tech with the transaction.
  - `payment` object, required
    - `network` string, required: CAIP-2 network the payment settled on.
    - `transaction` string, required: Settlement transaction hash; quote it to support.

## Other responses

- `402`: Payment required. x402 v2 terms (USDC on Base or Solana) in the PAYMENT-REQUIRED header; x402 v1 terms (USDC on Base) in the JSON body; an L402 Lightning invoice in WWW-Authenticate when offered. Pay and retry the same request.
- `429`: Too many requests from this address; try again later.
- `502`: The payment facilitator failed. If you were charged, email jorge@latitude10.tech with the transaction.
- `503`: Payments are briefly unavailable; nothing was charged.

---

[API](https://skmtc.dev/latitude10/apis/latitude-10.md) · [All operations](https://skmtc.dev/latitude10/apis/latitude-10/llms.txt) · [OpenAPI document](https://skmtc.dev/latitude10/apis/latitude-10/revisions/ef79d1f8e9c5?raw)