Developer kits · v1.0.3 · Oct 2026

Latitude 10 Agentify API

Make the API you already have agent-ready. Same process, same deploy.

An agent layer with MCP and x402 added to your existing API in the same process, with an agent-readiness score of 96

What is the Latitude 10 Agentify API?

Agents need to find your API, understand it, call it and maybe pay for it. That usually means writing an MCP server by hand, learning which discovery files agents look for, and deciding how to meter them. Agentify does it from the OpenAPI spec you already have, inside the app you already run: there is no second server to deploy.

A middleware for Express, Hono, Next.js and Fastify, and a CLI. An agent’s tool call runs through your own route handlers, so your auth, validation and business logic are the ones already tested. A readiness check tells you what a model will get wrong about your API before an agent does. Code you own; Node 22.

Want it installed for you? Ask for a fixed-price quote on the contact page.

You run this code and are responsible for it: review it, test it on staging, and check that it meets the laws, platform rules and security standards that apply to you before production. It is not legal, compliance or financial advice, and using it doesn’t make Latitude 10 your payment processor or service provider.

What do you get?

  • An MCP endpoint (both MCP versions) with one tool per operation: reads on, writes off until you turn them on
  • Tool calls run in-process through your own routes and auth middleware; about 0.1 ms of overhead
  • Discovery from one spec: llms.txt, the MCP server card, OpenAPI with agent hints, OAuth metadata, /.well-known/x402 and an /agent index
  • An agent-readiness score from 0 to 100 with fixes, and a command that drafts better descriptions
  • No spec yet? It drafts one from your routes, without running your code
  • Agents use your API’s own credentials, agent keys, or OAuth, including Amazon Cognito machine-to-machine tokens (how AWS AgentCore Gateway calls a target); rate limits and usage metering for agent traffic
  • Optional x402 pay-per-call for agents, settled only when your route succeeds; people with their own keys are never charged

Every kit includes

  • The full source code, yours to change
  • A setup wizard: node setup.mjs
  • A versioned release with a changelog
  • A download link that always serves the latest release

How do you set it up?

node setup.mjs

Makes a bundled Orders API agent-ready in the framework you pick (Express, Hono, Fastify or Next.js), with no API key: scores its thin spec (54/100) and improves it to 96, serves every discovery document, connects the official MCP client in both versions, calls a tool through the API’s own auth, rate-limits an agent key, takes an x402 payment and prints the usage.

You'll need: Node.js 22.13+ and an API on Express 4 or 5, Hono, Next.js or Fastify. Optional: Postgres, an OAuth provider, a wallet address for x402.

Can an AI agent buy it?

An AI agent can buy this product for $39 on its own, paying in USDC over x402:

https://latitude10.tech/api/agent-products/agentify-api

Or through our MCP server at https://latitude10.tech/mcp with buy_product. How agent payments work →

When an AI agent buys from Latitude 10, the person or company that runs the agent is the buyer and accepts the Terms of Service. Payments on a blockchain or over Lightning are final.