Latitude 10 Agentify API for PHP (Laravel)
Make the Laravel API you already have agent-ready. Same process, same deploy.

What is the Latitude 10 Agentify API for PHP (Laravel)?
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 (the one Scramble makes from your routes, or a file), inside the app you already run: there is no second server to deploy.
A Laravel package on a framework-free core, and Artisan commands. There is no code to add: the package puts its middleware in your global middleware, and an agent’s tool call runs through your own middleware, routes and controllers, so your auth (Sanctum included), form requests, policies and business logic are the ones already tested. It runs on PHP-FPM and Octane (FrankenPHP, Swoole, RoadRunner). A readiness check tells you what a model will get wrong about your API before an agent does. It is the PHP edition of Agentify API for Node.js: the same documents, the same wire formats, the same readiness score. Code you own; PHP 8.3 or newer and Laravel 12 or 13, with an OpenAPI document from Scramble or a file, and your app’s database for keys and usage: SQLite, Postgres or MySQL/MariaDB.
Agentify comes hosted or self-hosted. This kit is the self-hosted edition, inside the app you run. The hosted edition serves the same tools from your OpenAPI spec at a URL on latitude10.tech, free in a Latitude 10 workspace.
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 middleware, routes and controllers: Sanctum, form requests and policies included, controllers and closure routes 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? php artisan agentify:draft adds Scramble, which makes one from your routes
- Agents use your API’s own credentials, agent keys, or OAuth; 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
- PHP-FPM or Octane (FrankenPHP, Swoole, RoadRunner); your app’s own database, or a SQLite, Postgres, MySQL or MariaDB store of its own
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, java Setup.java for Java, or php setup.php --demo for PHP
- 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 PHP, the PHP edition of the Agentify API for Node, at parity with its 1.1.0: a Laravel 12 and 13 package,
latitude10/agentify-laravel, on a framework-free core,… - An MCP endpoint (both protocol eras) with a tool per operation, run in-process through your own middleware, routes and controllers, and discovery documents:
/llms.txt, server card, AI Catalog, OAuth… - On your routes: agent detection, agent keys, OAuth, rate limits, usage metering, x402 pay-per-call and
Idempotency-Key. Settings inconfig/agentify.php, read fromAGENTIFY_*variables. Stores:… - The Artisan commands:
agentify:init,draft,check,improve,sync,keys,usageandmigrate, with Node's output, andagentify:cacheandagentify:clear, whichoptimizeand… - A setup wizard (
php setup.php) that vendors the kit's Composer repository into your project, first and limited to the kit's packages, andphp setup.php --demoon the bundled Orders API.
What's in the zip
- latitude10-agentify-api-php/
- latitude10-agentify-api-php/CHANGELOG.md
- latitude10-agentify-api-php/LICENSE.md
- latitude10-agentify-api-php/README.md
- latitude10-agentify-api-php/THIRD-PARTY-NOTICES.md
- latitude10-agentify-api-php/VERSION
- latitude10-agentify-api-php/examples/
- latitude10-agentify-api-php/packages/
- latitude10-agentify-api-php/repository/
- latitude10-agentify-api-php/setup-demo.php
- latitude10-agentify-api-php/setup.php
How do you set it up?
php setup.php --demoMakes a bundled Laravel 13 Orders API agent-ready behind Sanctum, with no API key and no wallet: installs the kit into a copy of it, scores its thin spec (54/100) and improves it to 96, 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: PHP 8.3 or newer (with curl, json, mbstring, openssl, pdo and sodium) and a Laravel 12 or 13 app, under PHP-FPM or Octane (FrankenPHP, Swoole, RoadRunner), with Composer 2.2 or later. An OpenAPI document: the one Scramble makes from your routes, a file, or the one php artisan agentify:draft adds with Scramble. Keys and usage live in your app’s database by default, which needs SQLite, Postgres or MySQL/MariaDB (and its PDO extension). The demo needs Packagist to install its Laravel. Optional: 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-phpOr 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. If a kit won’t run on a version listed on its page, tell us within 30 days and we’ll fix it or refund you in the same asset, to the paying address.
Rather have it built for you? Our MCP implementation service uses these kits. →