Koskamo
Navigation

Revalidate rights status for existing content

The agent pays to re-check a resource's rights against a previous checkpoint, detecting any changes in declaration or availability to maintain compliance.

How it works

Moves money or places ordersOperations and infrastructure

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.

Prompt

Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.

Prompt for Revalidate rights status for existing content
Revalidate rights for https://example.com/article using previous checkpoint data. Use deep tier and approve payment. Return the new report.

MCP servers it needs

Source

The vendor page this playbook is drawn from, and the passage that supports it.

Compare one resource to its authentic prior gateway checkpoint
AcqPath MCP documentation

Each playbook is drawn from the vendor page it cites and reviewed by Koskamo before it is published. Koskamo does not run these servers or your agent: check what each tool will do before you let it act on your accounts.

More playbooks like this