Can I look up a container by its container number?

Yes. GET /container/{containerNumber} returns the technical record including tare weight, maximum gross mass, and ISO 6346 size-type code. You can also use GET /tare_kg/{containerNumber} or GET /max_gross_mass_kgs/{containerNumber} to fetch specific properties without loading the full record.

How do I verify a BIC owner code?

Call GET /codes/{bicCode} with the four-letter BIC prefix. The response includes the registered holder details, which lets you confirm the container's ownership before accepting it into your yard or onto a vessel.

How do I upload fleet data through Jentic?

Search Jentic for 'upload container fleet', load POST /container, and execute with the upload payload. Then poll GET /uploads/{uploadId} until processing completes. With the SDK: pip install jentic, then SearchRequest, LoadRequest, ExecutionRequest in an async flow.

Is there a sandbox environment for the BIC-BoxTech API?

Yes - the spec exposes a UAT host at https://uat.bic-boxtech.org/api/v2.0 alongside production at https://app.bic-boxtech.org/api/v2.0. Use UAT for integration testing before promoting to production credentials.

Can I limit what my agent is allowed to do with the BIC-BoxTech API?

Yes. Because you run Jentic One yourself, your own rules decide which BIC-BoxTech operations and credentials the agent may use. You can allow read-only lookups such as GET /container/{containerNumber}, GET /tare_kg/{containerNumber}, and GET /codes/{bicCode} while withholding fleet registration via POST /container, so container uploads are excluded unless you add them. Since the container number sits in the URL path, a rule can also pin the agent to lookups for a specific container.