Anvyl

Enable the Anvyl connector in your fastn dashboard, then let each customer authenticate their own Anvyl account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Anvyl client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own Anvyl account and only ever sees their own shipments, tracking events and orders. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.

Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a purchase order's status and history before answering a delivery question.

fastn does. When Anvyl changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.

Yes. Shipment and tracking events are read per customer and can trigger your workflows, so status changes surface in your product instead of your users checking a carrier site.

Whatever Anvyl actually holds. Where it moves goods, that is shipment and tracking events, read per customer and delivered as they land. Where it holds stock, levels can be read on demand or kept in step through events, so your product is not deciding on a stale count. Where it carries orders and documents between trading partners, it is the acknowledgement, ship notice or status change that says what moved.

A common starting point: read purchase orders and their line items into your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Anvyl does not change your per-connector cost. You can start free with 3 connected accounts.