Developers
Programmable customs compliance for cross-border exports.
Plan exports. Execute exports. Inspect export state.
Build customs compliance automation into apps, AI agents, and supply chain systems.
Customs classification, documentation, and broker handoff stay in the protocol layer.
Docs Posture
Start with the protocol model, then move directly into implementation.
Read the lifecycle first. Then move into /docs/quickstart and the API reference.
Start Here
Why developers use EntryGo
Customs validation, broker routing, warehouse coordination, and artifact generation should not be rebuilt in every client.
EntryGo centralizes the protocol layer. Apps, internal tools, and AI agents stay focused on their own surfaces.
How developers start
The export API is organized around three endpoints. Each stage is explicit for direct integrations, operator tooling, and AI-agent workflows.
Read /protocol. Run the first flow in /docs/quickstart. Use the API reference for endpoint detail.
Build an export plan with readiness, compliance, and routing inputs.
Run the export workflow and generate broker-ready records and notifications.
Read export state, artifacts, and operational outcomes through one surface.
What developers can build
REST API
A clean export API for planning, executing, and inspecting cross-border export workflows.
TypeScript SDK
Build programmable exports into modern commerce systems with a typed integration surface.
Python SDK
Connect internal tools, data workflows, and operational systems to the export automation API.
CLI
Inspect and operate the protocol from the terminal during development and integration work.
Webhooks / export events
Subscribe to auditable export events and keep downstream systems in sync with protocol state.
Why build on EntryGo
Predictable workflow model
Use a simple plan, execute, inspect lifecycle instead of inventing export state from scratch.
Shared export logic
Keep compliance, routing, and artifact generation in one protocol layer rather than every integration.
Auditable export events
Track export execution through consistent records instead of reconstructing history from partner threads.
Cleaner integrations
Build lighter clients because the cross-border export API handles orchestration centrally.
AI-agent compatibility
Give machine clients explicit states and inspectable outputs through a stable customs automation API.
Common build targets
Merchant-side export automation
Warehouse-originated planning flows
Broker submission adapters
Operator surfaces and internal tools
AI-agent export orchestration
Event-driven downstream integrations
One protocol, many clients
EntryGo keeps export orchestration in one protocol engine so commerce apps, automations, and agents can all work against the same model. That makes integrations cleaner and makes programmable exports easier to maintain over time.