How to Use CBP forced labor dataset publication status in Muse Code
Returns publication version information for CBP's Withhold Release Orders and Findings dataset. Use it to check for a changed publication before refreshing searches or reviewing saved orders.
Prompts to try with CBP forced labor dataset publication status in Muse Code
Copy an example into Muse Code, or ask in your own words.
Use CBP forced labor dataset publication status to compare the current publication with the version saved in our Indonesia sourcing report and show whether the report needs a data refresh.
Use CBP forced labor dataset publication status to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from CBP forced labor dataset publication status and tell me what changed since last week.
Check CBP forced labor dataset publication status and summarize what you find in three bullet points.
Pull the newest data from CBP forced labor dataset publication status and give me the result as a table.
How to set up CBP forced labor dataset publication status in Muse Code
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Install Muse Code
curl -fsSL https://dev.meta.ai/install.sh | bash
- Ask Muse to add the server
Start muse and ask:
Add the Spiral MCP server at https://api.spiral.ai/mcp
- Sign in
In your terminal, run:
muse mcp login spiral
Use the Spiral skill
- Send Muse Code this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run CBP forced labor dataset publication status
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "cbp-gov/withhold-release-orders/source_status", "input": {} }'
Then paste one of the prompts above: Muse Code finds CBP forced labor dataset publication status on Spiral, shows the price and runs it.
CBP forced labor dataset publication status providers and prices
Spiral runs CBP forced labor dataset publication status through Alexandria. Open a card for today's price, with every fee included.
What can you do with CBP forced labor dataset publication status in Muse Code?
Build a sourcing review table that connects CBP orders to covered merchandise and effective dates. Use publication checks to refresh the project's data, searches to collect records, and individual lookups to populate order views.
Prepare a palm oil sourcing review
Check the publication version, search Indonesian palm oil records, and inspect the matching orders. Build a review table of named entities, covered merchandise, effective dates, and current statuses.
Refresh a customs briefing
Compare the publication version with the previous review, collect the latest records, and examine changed orders. Give the customs team a short briefing on changes to covered goods and order statuses.
Compare enforcement across sourcing countries
Confirm the dataset publication, collect records for Malaysia and Indonesia, and inspect the orders behind each comparison. Summarize affected merchandise while keeping WROs and Findings separate.
Review a merchandise category
Use the publication check to decide whether a cotton review needs refreshing. Search the published records and examine each relevant order's merchandise description and status before preparing the review.
Build an enforcement timeline
Identify the publication used, collect orders for a sourcing country, and read the selected records. Arrange them by effective date to explain when the published actions became enforceable.
Update an order reference library
Check whether CBP has changed its publication, refresh the record index, and re-read saved orders. Keep merchandise descriptions, statuses, and available notice references together for trade researchers.
More on CBP forced labor dataset publication status and Muse Code
Overview
CBP forced labor dataset publication status in other agents
Questions about CBP forced labor dataset publication status in Muse Code
Can Muse Code use CBP forced labor dataset publication status?
Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run CBP forced labor dataset publication status like any built-in tool.
How much does CBP forced labor dataset publication status cost in Muse Code?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse Code plan is separate.
Do I need an Alexandria account to use CBP forced labor dataset publication status in Muse Code?
No. Spiral runs CBP forced labor dataset publication status on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up CBP forced labor dataset publication status in Muse Code?
About two minutes: install Muse Code, then ask Muse to add the server, then sign in.
Does Muse Code wait while CBP forced labor dataset publication status runs?
CBP forced labor dataset publication status runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.
How often does CBP update these records?
CBP updates the dashboard as needed when orders are added, removed, or modified. It does not publish a fixed daily or monthly refresh schedule.
How far back does the published coverage go?
CBP describes its dashboard as covering active WROs and Findings issued from 1950 to the present. That describes historical order coverage, rather than an archive of every past publication.
Does a WRO mean CBP conclusively established forced labor?
A WRO uses a reasonable but nonconclusive evidentiary standard. A Finding uses a conclusive standard, so the two action types should remain separate in reports.
What is the practical difference between a WRO and a Finding?
A WRO permits CBP to detain the covered products. A Finding permits seizure of the covered products.
What does an order's effective date mean?
It is the date the WRO or Finding became enforceable by CBP. Use it when comparing enforcement timing, rather than treating it as the dataset's refresh date.
Start using CBP forced labor dataset publication status in Muse Code
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Muse Code:
set up https://spiral.ai/SKILL.md


