omnibox.app

What it is

Omnibox（贸易百宝箱）positions itself as cross-border compliance and intelligent customs infrastructure for international trade companies and AI Agents. It packages product HTS/HSCode classification, full-scope tariff estimation, U.S. Trade.gov CSL sanctions/restricted-entity screening, and CBP official customs ruling search into callable tools. Its target users include import/export businesses, ERP/customs declaration software, cross-border e-commerce platforms, and agent developers.

Core features and developer access

From a developer tooling perspective, its biggest highlight is that it offers both MCP and REST OpenAPI 3.0. On the MCP side, it can be connected via an SSE endpoint to MCP-compatible clients such as Claude Desktop and Cursor, with three built-in tool categories: classify, screen_party, and search_cbp_rulings. On the REST side, it provides endpoints such as /api/v1/compliance/classify, /screen, and /rulings/search, along with cURL examples, Swagger UI, and an online testing console. The page also mentions Cloudflare edge computing, vector search, and a D1 tariff rules database, but does not go into detail on the architecture, availability metrics, or benchmarking methodology.

Pricing and ecosystem

The page repeatedly emphasizes “free forever,” “completely free,” and “zero cost.” Core APIs are protected by API Key, and users need to create an App in the developer console. For early-stage developers and small to midsize trade teams, the trial cost is very low. However, it does not disclose request quotas, concurrency limits, SLA, paid support, or enterprise plan terms, so these should be confirmed before using it in production. On the ecosystem side, it says it supports Claude Desktop, Cursor, Dify, and LangChain/LlamaIndex, and plans Skill cards for Coze, Dify, and GPTs, though this module is still marked Coming Soon.

Pros, cons, and who it is for

Its strengths are a focused use case and a relatively high degree of API standardization, turning complex customs workflows into atomic capabilities that AI Agents can call. It is appealing for teams that want to quickly validate an “AI customs assistant.” The main weakness is limited transparency: it does not clarify whether it is open source, whether self-hosting is available, what its data privacy policies are, who operates the service, how error codes work, what limits apply, or what commercial guarantees are provided. Coverage also appears to center mainly on U.S. HTS, CSL, and CBP, while broader multi-country compliance capabilities remain unclear. It is best suited for international trade SaaS products, customs declaration systems, cross-border seller tools, and internal enterprise Agents for prototyping or lightweight integration.

Access from China and alternatives

The page does not provide information about access from mainland China, payment, or ICP filing/registration, so actual availability should be verified through network testing and is currently considered unknown. If access is limited, alternatives include using official Trade.gov/CBP data sources directly, building an internal rules database, or adopting a mature customs/trade compliance SaaS platform.