The agent pays to re-check a resource's rights against a previous checkpoint, detecting any changes in declaration or availability to maintain compliance.
The agent retrieves a previously stored signed checkpoint for a specific resource. It constructs a revalidation request to the AcqPath server, including the previous checkpoint, resource scope, and original parameters (purpose, geo, user_class). The agent specifies the tier (fresh or deep) and ensures the payment is approved via x402 signature. The server performs a new observation. The agent receives the new report and compares it to the previous checkpoint. If the status is 'CHANGED' or 'UNKNOWN', the agent flags the content for review. This ensures that any updates to publisher declarations are caught.
- Category: Operations and infrastructure
- Effect: Moves money or places orders
- MCP servers: AcqPath MCP (https://koskamo.com/explore/acqpath-mcp)
- Source: AcqPath MCP documentation (https://developers.getacqpath.com/examples/GATEWAY.md)
- Source quote: "Compare one resource to its authentic prior gateway checkpoint"
- Playbook page: https://koskamo.com/explore/use-cases/revalidate-rights-status-for-existing-content
Prompt: Revalidate rights for https://example.com/article using previous checkpoint data. Use deep tier and approve payment. Return the new report.