Laxmikant Sharma
I work on how software agents hire and pay each other: identity, payments, and verification. Distinguished Engineer at Walmart Global Tech, and author of PACT, an IETF Internet-Draft that binds agent work to money to proof.
flagship
[standard]
PACT: Liability and Settlement for Autonomous Agent Contracts
An IETF Internet-Draft that makes one agent financially answerable to another: liability as a required, co-signed member of the contract, propagated through the subcontract tree.
latest
[writing]
What Would a Markets Regulator Ask of an Agent?I tried to file one agent tool call as an order record under the EU trading rules. Of the eighteen fields that apply, six map to something standard and four have no source at all. Those rules have been binding since 2018, and in February the regulator pointed them at GenAI.
[writing]
How Long Does a Revoked Agent Keep Working?I tried to write down the formula for revocation latency and it kept being wrong in instructive ways. The corrections come from validator source code: a five-minute grace on expired tokens in .NET, streams that outlive their token by design, and a 12-hour JWKS refresh on the one lever that actually works. With runnable experiments.
[writing]
Agent Accountability Starts With "On Whose Authority"Only two fields are Required on the OpenTelemetry span that records an agent taking an action. Not who authorized it, not what it was allowed to do, not what it sent. Here's the gap, field by field, and what to do about it.
[writing]
Agents Are Speedrunning the History of RPCWhen a tool call dies mid-flight, neither MCP nor A2A can tell you whether it executed, and no retry can prove it is the same request. RPC solved this in 1984. Three changes close the gap.
[note]
This site is home nowWhy everything I publish will land at laxsharma.com first.
[writing]
When Agents Hire Agents: PACT, the Missing Layer 4 of the Agentic WebA2A moves tasks without prices, x402 moves money unconditionally, AP2 authorizes without verifying. PACT adds the missing object: the Verifiable Task Contract.
[writing]
The Agentic Web Is Being Wired Right Now: A Field Guide to MCP, A2A, Skills, and Agent PaymentsA field guide to the protocols wiring the agentic web: MCP for tools, A2A for agent-to-agent work, Skills for know-how, and the three-way fight over payments.
[writing]
Can You Trust an Autonomous Agent? The Identity and Delegation Layer Behind MCP, A2A, and AP2Four questions a bearer token cannot answer: agent identity, authorization flows, delegation chains, and accountability, each mapped to its standard.