Tarifflo: Customs, as an API

The entry starts before the filing screen

A customs entry starts with an invoice, a packing list and a bill of lading. Someone has to turn those documents into classified line items, required agency records and a filing ready for review.

Copying the same shipment between an operating system and a separate filing tool adds another place for a field to go wrong.

Tarifflo is building customs infrastructure around an API. A broker or importer can prepare the entry from its existing systems, validate it and submit under its own filer code. [1][2]

The product joins the work before submission with the responses that arrive afterward. A person reviews and approves the entry before it goes out. [1]

From the broker’s system to CBP

Tarifflo’s ABI product handles entry-summary preparation and transmission to U.S. Customs and Border Protection. ABI is the electronic filing interface; ACE is the CBP system receiving the transactions. [2]

Tarifflo validates the structured records before submission. The checks cover fields such as manufacturer identifiers, tariff classifications and required agency records. [2]

The API lets the filing remain part of a broker’s existing software. Tarifflo also supports a dashboard for review and a Claude integration through MCP for preparing entries from documents. [1][3]

A licensed broker or self-filing importer keeps its own filer identity. Tarifflo supplies the software and transmission layer. [1][4]

One entry, from preparation to response

Consider a broker filing from its own operating system. It sends an entry summary to Tarifflo’s API. Validators check it before Tarifflo transmits it to CBP. [4]

The broker can correct a missing or malformed field before submission, using the same entry data instead of typing the shipment into another application. [2][4]

After transmission, the entry’s timeline brings together acknowledgements, status changes and subsequent messages. The operating team can follow progress in the system where the work began. [1][2]

Tarifflo’s developer tools include a REST API and webhooks, so a shipment’s filing status can feed back into the broker’s own application. [3]

Built by a customs broker

Founder Bryce Judy is a licensed customs broker and data scientist. Before Tarifflo, Judy worked at KPMG US on customs classification and international tax. [5]

Tarifflo joined Y Combinator’s Summer 2026 batch. Its customers are brokers and importers doing the recurring work of preparing entries, checking duties and tracking customs responses. [1][5]

The broader platform also audits past entries for classification and duty errors. When an overpayment is found, the filing tools support work on corrections alongside the original entry records. [1][2]

A path into live filing

ABI is in private beta, with a waitlist and sandbox onboarding. Live filing requires approval of the filer’s connection by its CBP client representative. [1][2]

For existing filers, Tarifflo helps prepare and track that connection request. For importers becoming self-filers, the team guides the setup and required documents. [1]

The direction is one entry lifecycle: prepare from source documents, review the classification, validate the records, file and follow the response. Audit and recovery sit alongside that same customs data. [1][2]

The bigger picture

Brokers and importers need an entry to move from their shipment data into customs and back with a clear status.

Tarifflo’s approach puts that work inside the systems they already operate. Its bet is that filing, validation and customs intelligence can share the same infrastructure. [1][3]

Customs becomes an API the business can build around.