Sulat.com / Writing on AISaturday, November 21, 2026
Agent Engineering/21 November 2026

New Laravel package serves AI agents over A2A, but PHP already had A2A SDKs

Developer Tibor's a2a-laravel serves Laravel AI SDK agents over the A2A protocol with one route. The 81/81 conformance claim leaves out 11 skipped tests, and other PHP A2A SDKs already exist.

Glossy 3D red Laravel logo and purple PHP logo facing each other, joined by a glowing teal stream of data packets

At a glance

  • Tibor says his a2a-php SDK and a2a-laravel package both pass the official A2A conformance suite; the READMEs list 81 MUST and 9 SHOULD tests passed, none failed, and 11 and 1 skipped.
  • The a2a-laravel README says one Route::a2a() call serves a Laravel AI SDK agent over JSON-RPC, HTTP+JSON and server-sent events, with its agent card at /.well-known/agent-card.json.
  • Packagist already lists PHP A2A SDKs, including praveendias1180/a2a-php 1.0.3 from 14 October 2026, so Tibor's packages aren't the first for PHP.
  • Both of Tibor's packages are at version 0.1.0, need PHP 8.5, aren't on Packagist yet and don't support gRPC.

Developer Tibor has released two PHP packages for the Agent2Agent (A2A) protocol: a2a-php, an SDK, and a2a-laravel, a Laravel package built on top of it. Tibor’s post on X, dated 20 November, says PHP can now speak A2A and that both packages pass the official conformance suite.

A2A is an open protocol that lets agents built on different frameworks call each other over HTTP. Each agent publishes an agent card that lists its skills. The two GitHub repositories, tibor-src/a2a-php and tibor-src/a2a-laravel, were both created on 20 November and carry a 0.1.0 changelog entry with the same date.

Tibor’s announcement of a2a-php and a2a-laravel on X, 20 November 2026.

What a2a-laravel does

According to its README, a2a-laravel adds a Route::a2a() macro that serves JSON-RPC, HTTP+JSON, server-sent event streaming and the agent card from a single call. Point the a2a.agent config key at a class from the Laravel AI SDK and the package takes the card name, instructions and tools-as-skills from that class.

It also works the other way. A2A::tool() wraps a remote A2A agent as a tool that your own Laravel AI agent can call. Underneath, the changelog lists four task stores (memory, cache, file and Eloquent), queued execution, push notification jobs that retry three times, and Sanctum or Passport bearer auth. A2A::fake() lets a test check what the app sent to a remote agent.

See the route and config from the README
Code
use Illuminate\Support\Facades\Route;

Route::a2a();        // JSON-RPC, HTTP+JSON, SSE, /.well-known/agent-card.json
Route::a2a('a2a');   // or mount it under a prefix

// config/a2a.php
'agent' => App\Ai\SupportAgent::class,
A Laravel AI agent class flows into Route::a2a(), which serves JSON-RPC, HTTP+JSON, SSE streaming and an agent card; no gRPC
One Route::a2a() call puts a Laravel AI agent on two transports, with streaming and a card.

What 81/81 covers

The post says both packages pass 81/81 MUST tests and 9/9 SHOULD tests. The READMEs give the fuller count from the official a2a-tck suite: 81 MUST tests passed, none failed and 11 were skipped, while 9 SHOULD tests passed, none failed and 1 was skipped. The runs covered JSON-RPC and HTTP+JSON. Nothing failed, but 12 of the 102 listed tests didn’t run.

ModeBindingsMUSTSHOULD
SyncJSON-RPC and HTTP+JSON81 passed, 0 failed, 11 skipped9 passed, 0 failed, 1 skipped
QueuedJSON-RPC and HTTP+JSON81 passed, 0 failed, 11 skipped9 passed, 0 failed, 1 skipped
Results as listed in the a2a-laravel README, run against its Testbench workbench.
Two bars: 81 of 92 MUST tests passed and 11 skipped; 9 of 10 SHOULD tests passed and 1 skipped; none failed
Nothing failed, but 11 MUST tests and 1 SHOULD test never ran.

The a2a-php README adds that seven MUST checks (client TLS, card signing and custom binding versioning) and two SHOULD TLS checks can’t be automated, so they were left as manual checks. The suite’s own README says a 100% automated score doesn’t establish full conformance.

PHP already had A2A SDKs

Packagist lists several earlier PHP implementations. neuron-core/a2a, from Valerio Barbera, reached 1.0.0 on 21 October 2025 and shows more than 6,700 installs. vbcherepanov/a2a-php-sdk 1.0.0 followed on 15 September 2026, covering A2A 1.0.0 over JSON-RPC, HTTP+JSON and gRPC.

praveendias1180/a2a-php 1.0.3 landed on 14 October 2026 with its own Laravel bridge, which also offers Route::a2a(). Its README reports passing the same suite at the MUST, SHOULD and MAY levels. What Tibor’s changelog lists as new is the Laravel AI SDK bridge: serving a Laravel AI agent over A2A and calling a remote agent as a Laravel AI tool. The praveendias1180 README doesn’t mention the Laravel AI SDK.

Four PHP A2A packages with release dates and minimum PHP versions; the tibor-src package is the newest and not yet on Packagist
Tibor’s package is the newest of the four listed here and the only one not on Packagist yet.

Before you install it

Both of Tibor’s packages are at 0.1.0 under an MIT licence. They need PHP 8.5, which is well above the PHP 8.2 minimum on praveendias1180’s SDK, and the Laravel package needs Laravel 12 or 13. Neither is on Packagist, so Composer needs both GitHub repositories added as VCS sources. Neither supports gRPC.

The a2a-laravel README lists three follow-ups: an optional laravel/mcp bridge, live SSE streaming while a queue worker is still running, and a Packagist listing.


Sources


Discover more from Sulat AI & Tech News

Subscribe to get the latest posts sent to your email.