Verify peptide regulatory compliance for shipping
A definitive compliance decision (allow, deny, or require prescription) for a specific peptide, actor, and destination jurisdiction, backed by source URLs and rule-set versions.
How it works
The agent first resolves the target jurisdiction using the ship-to code to identify the correct regulatory framework. It then resolves the actor class to determine the appropriate channel and communication class. Finally, it calls gate_transaction with the substance name, pathway, actor class, and jurisdiction to retrieve the regulatory status. The agent should verify the 'result' field and review the 'source_url' for the specific regulation cited.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Check if I can ship 'tirzepatide' as a licensed medicine to a dispenser in Florida, US. First resolve the jurisdiction for US-FL, then resolve the actor class for 'dispenser', and finally gate the transaction.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
Gate order: resolve_jurisdiction → resolve_actor → gate_transaction.A2A Peptides MCP documentation