Latitude 10 Agentify API for Java (Spring Boot)

What is the Latitude 10 Agentify API for Java (Spring Boot)?

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 document you already have (a file, or the one your app already serves), inside the app you already run: there is no second server to deploy.

A Spring Boot starter for Spring MVC and Spring WebFlux, and the agentify.jar command line for Maven and Gradle builds. There is no code to add: the starter sits in front of Spring Security, and an agent’s tool call runs through your own filters and controllers, so your auth, validation and business logic are the ones already tested. It works in a GraalVM native image. A readiness check tells you what a model will get wrong about your API before an agent does. It is the Java edition of Agentify API for Node.js: the same documents, the same wire formats, the same readiness score. Code you own; Java 17 or newer and Spring Boot 4, with an OpenAPI document, and a database and its JDBC driver for persistent stores: SQLite, Postgres, MySQL or MariaDB.

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 filters and controllers, Spring Security included: annotated controllers and functional endpoints alike
• Discovery from one document: llms.txt, the MCP server card, OpenAPI with agent hints, OAuth metadata, /.well-known/x402 and an /agent index, in the Node.js edition’s wire formats
• An agent-readiness score from 0 to 100 with fixes, the same score as the Node.js edition, and a command that drafts better descriptions
• No OpenAPI document yet? agentify.jar draft adds springdoc, which serves one made from your controllers
• Agents use your API’s own credentials, agent keys, or OAuth, including Amazon Cognito machine-to-machine tokens; 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
• Spring MVC or WebFlux, in a GraalVM native image too; SQLite, Postgres, MySQL or MariaDB stores, or your app’s own DataSource

Every kit includes

• The full source code, yours to change
• A setup wizard: node setup.mjs, uv run setup.py for Python, dotnet run setup.cs for .NET, or java Setup.java for Java
• A versioned release with a changelog
• A download link that always serves the latest release

What's new in v1.0.0

• First release of the Agentify API for Java, the Java edition of the Agentify API for Node, at parity with its 1.1.0: a Spring Boot 4 starter for Spring MVC and Spring WebFlux, and the agentify.jar…
• An MCP endpoint (both protocol eras) with a tool per operation, run in-process through your own filters and controllers, and discovery documents: /llms.txt, server card, AI Catalog, OAuth and x402…
• On your routes: agent detection, agent keys, OAuth, rate limits, usage metering, x402 pay-per-call and Idempotency-Key. agentify.max-argument-values (default 10,000) is Node 1.1.0's…
• The agentify.jar command: init vendors the kit's Maven repository into your project, edits Maven or Gradle builds, and stops behind a Maven mirror that would hide it; then draft, check,…
• Java 17 to 25, Spring Boot 4.0 and 4.1, native images with GraalVM 25, and a setup wizard (java Setup.java) on the Orders API for Spring MVC and for Spring WebFlux.

What's in the zip

• latitude10-agentify-api-java/
• latitude10-agentify-api-java/.gitignore
• latitude10-agentify-api-java/.mvn/
• latitude10-agentify-api-java/CHANGELOG.md
• latitude10-agentify-api-java/LICENSE.md
• latitude10-agentify-api-java/README.md
• latitude10-agentify-api-java/Setup.java
• latitude10-agentify-api-java/THIRD-PARTY-NOTICES.md
• latitude10-agentify-api-java/VERSION
• latitude10-agentify-api-java/agentify-cli/
• latitude10-agentify-api-java/agentify-core/
• latitude10-agentify-api-java/agentify-jdbc/
• latitude10-agentify-api-java/agentify-parity/
• latitude10-agentify-api-java/agentify-spring-boot-starter/
• latitude10-agentify-api-java/agentify-spring-boot/
• latitude10-agentify-api-java/agentify.jar
• latitude10-agentify-api-java/examples/
• latitude10-agentify-api-java/lib/
• latitude10-agentify-api-java/mvnw
• latitude10-agentify-api-java/mvnw.cmd
• latitude10-agentify-api-java/pom.xml
• latitude10-agentify-api-java/repository/

How do you set it up?

Makes a bundled Orders API agent-ready with Spring MVC or Spring WebFlux behind Spring Security, with no API key: runs agentify.jar init on it, scores its thin spec (54/100) and improves it to 96, builds and boots it, serves every discovery document, connects an 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: Java 17 or newer and a Spring Boot 4 app on Spring MVC (Tomcat) or Spring WebFlux (Reactor Netty), built with Maven or Gradle. An OpenAPI document: a file, or the one your app serves with springdoc, or the one agentify.jar draft adds. A store that outlives the process needs a database and its JDBC driver in your app: SQLite, Postgres, MySQL or MariaDB, or your app’s own DataSource (the memory store is for development). The wizard needs Maven Central to build its example. Optional: an OAuth provider, a wallet address for x402.