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.
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.
- Category: Operations and infrastructure
- Effect: Read-only
- MCP servers: A2A Peptides MCP (https://koskamo.com/explore/a2a-peptides-mcp)
- Source: A2A Peptides MCP documentation (https://a2a-peptides.ai/docs)
- Source quote: "Gate order: resolve_jurisdiction → resolve_actor → gate_transaction."
- Playbook page: https://koskamo.com/explore/use-cases/verify-peptide-regulatory-compliance-for-shipping
Prompt: 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.