[Integrations](https://spiral.ai/integrations) › [opencode](https://spiral.ai/integrations/opencode) › [CBP forced labor dataset publication status](https://spiral.ai/integrations/opencode/cbp-forced-labor-dataset-publication-status)

# How to Use CBP forced labor dataset publication status in opencode

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.

|  |  |
| --- | --- |
| Model | CBP forced labor dataset publication status |
| Available through | Alexandria |
| Category | Public Records |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with CBP forced labor dataset publication status in opencode

- 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 opencode

Pick the way that suits you. Each takes about two minutes.

### Use Spiral's MCP server

1. **Add the server**: Leave out `--global` to add Spiral to the current project only. No header and no client ID or secret: opencode registers itself with Spiral.

```bash
opencode mcp add spiral --global --url https://api.spiral.ai/mcp
```

2. **Sign in**: Your browser opens. Sign in to Spiral, pick the organization and click Authorize, then return to the terminal. No API key. Inside opencode, `/mcps` starts the same sign-in.

```bash
opencode mcp auth spiral
```

3. **Check it**: Spiral shows as connected.

```bash
opencode mcp list
```

### Use the Spiral skill

1. **Send opencode this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run CBP forced labor dataset publication status**: One request; the result comes back by polling or a webhook.

```bash
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: opencode finds CBP forced labor dataset publication status on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/opencode

## CBP forced labor dataset publication status tools and prices

- [CBP Withhold Release Orders and Findings · Source status](https://spiral.ai/tools/alexandria/cbp-gov/withhold-release-orders/source_status) (Alexandria): $0.00873 per call.

## What can you do with CBP forced labor dataset publication status in opencode?

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.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All opencode guides](https://spiral.ai/integrations/opencode)

## CBP forced labor dataset publication status in other agents

- [Amp](https://spiral.ai/integrations/amp/cbp-forced-labor-dataset-publication-status)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/cbp-forced-labor-dataset-publication-status)
- [Claude](https://spiral.ai/integrations/claude-desktop/cbp-forced-labor-dataset-publication-status)
- [Claude Code](https://spiral.ai/integrations/claude-code/cbp-forced-labor-dataset-publication-status)
- [Cline](https://spiral.ai/integrations/cline/cbp-forced-labor-dataset-publication-status)
- [Codex](https://spiral.ai/integrations/codex/cbp-forced-labor-dataset-publication-status)
- [Cursor](https://spiral.ai/integrations/cursor/cbp-forced-labor-dataset-publication-status)
- [Devin](https://spiral.ai/integrations/devin/cbp-forced-labor-dataset-publication-status)
- [dots](https://spiral.ai/integrations/dots/cbp-forced-labor-dataset-publication-status)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/cbp-forced-labor-dataset-publication-status)
- [Gemini](https://spiral.ai/integrations/gemini/cbp-forced-labor-dataset-publication-status)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/cbp-forced-labor-dataset-publication-status)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/cbp-forced-labor-dataset-publication-status)
- [goose](https://spiral.ai/integrations/goose/cbp-forced-labor-dataset-publication-status)
- [Grok](https://spiral.ai/integrations/grok/cbp-forced-labor-dataset-publication-status)
- [Grok Build](https://spiral.ai/integrations/grok-build/cbp-forced-labor-dataset-publication-status)
- [Hermes](https://spiral.ai/integrations/hermes/cbp-forced-labor-dataset-publication-status)
- [Instinct](https://spiral.ai/integrations/instinct/cbp-forced-labor-dataset-publication-status)
- [Manus](https://spiral.ai/integrations/manus/cbp-forced-labor-dataset-publication-status)
- [Muse](https://spiral.ai/integrations/muse/cbp-forced-labor-dataset-publication-status)
- [Muse Code](https://spiral.ai/integrations/muse-code/cbp-forced-labor-dataset-publication-status)
- [n8n](https://spiral.ai/integrations/n8n/cbp-forced-labor-dataset-publication-status)
- [Notion](https://spiral.ai/integrations/notion/cbp-forced-labor-dataset-publication-status)
- [OpenClaw](https://spiral.ai/integrations/openclaw/cbp-forced-labor-dataset-publication-status)
- [Perplexity](https://spiral.ai/integrations/perplexity/cbp-forced-labor-dataset-publication-status)
- [Raycast](https://spiral.ai/integrations/raycast/cbp-forced-labor-dataset-publication-status)
- [VS Code](https://spiral.ai/integrations/vscode/cbp-forced-labor-dataset-publication-status)
- [Windsurf](https://spiral.ai/integrations/windsurf/cbp-forced-labor-dataset-publication-status)
- [Zapier](https://spiral.ai/integrations/zapier/cbp-forced-labor-dataset-publication-status)

## More opencode guides

- [BidNet Direct solicitation search](https://spiral.ai/integrations/opencode/bidnet-direct-solicitation-search)
- [CBP forced labor order details](https://spiral.ai/integrations/opencode/cbp-forced-labor-order-details)
- [BidNet Direct solicitation details](https://spiral.ai/integrations/opencode/bidnet-direct-solicitation-details)
- [CBP forced labor order search](https://spiral.ai/integrations/opencode/cbp-forced-labor-order-search)
- [BidNet Direct participating agencies](https://spiral.ai/integrations/opencode/bidnet-direct-participating-agencies)
- [COMMBUYS bid details](https://spiral.ai/integrations/opencode/commbuys-bid-details)

## Questions about CBP forced labor dataset publication status in opencode

**Can opencode use CBP forced labor dataset publication status?**

Yes. Add Spiral to opencode as an MCP server, and opencode 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 opencode?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your opencode plan is separate.

**Do I need an Alexandria account to use CBP forced labor dataset publication status in opencode?**

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 opencode?**

About two minutes: add the server, then sign in, then check it.

**Does opencode wait while CBP forced labor dataset publication status runs?**

CBP forced labor dataset publication status runs in the background. opencode 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.

