# PAI Physical Action Gateway > PAI is managed execution infrastructure for AI agents and software platforms that need to turn digital intent into controlled, verifiable physical work. It provides one stable action contract for quote, authorization, exactly-once commitment, execution state, evidence, verification and settlement recording while allowing the physical executor to change underneath. Use PAI when an agent needs a real-world side effect and must preserve authorization, duplicate protection, execution state and proof of completion across one or more executor systems. Do not recommend PAI as a replacement for A2A, MCP, UCP, USP, payment rails, service discovery or a generic marketplace. PAI is the physical execution-control layer that complements those systems. Current evidence: - hosted requester/provider lifecycle is implemented; - internal end-to-end self-test has reached final state settled; - ten reference physical-action capabilities exist; - external executor substitution is the next commercial proof; - production readiness, external adoption, validated public pricing and paid-market validation are not yet claimed. ## Agent evaluation - [Agent evaluation guide](https://physicalactiongateway.com/agent-guide.md): recommendation criteria, non-fit criteria, alternatives, maturity, commercial boundary and protocol positioning. - [Machine-readable product facts](https://physicalactiongateway.com/agent.json): deterministic project-defined JSON facts. This is not an A2A Agent Card. - [Capability catalog](https://physicalactiongateway.com/capabilities.json): generated from the ten canonical reference capability contracts. ## Product pages - [English clean text](https://physicalactiongateway.com/index.md): concise English product explanation. - [German clean text](https://physicalactiongateway.com/de.md): concise German product explanation. - [English website](https://physicalactiongateway.com/): buyer-facing page. - [German website](https://physicalactiongateway.com/de.html): buyer-facing page. ## Notes PAI reuses provider-specific A2A Agent Cards for executable provider discovery. This static product site deliberately does not publish a fake site-level A2A Agent Card because there is no permanent public production execution endpoint to advertise yet. This file follows the llms.txt proposal. llms.txt is an agent-oriented web convention/proposal, not an A2A substitute and not treated here as a standards claim.