Skip to main content

Managing your Tollbit Edge Integration

Arc XP is excited to announce that we now have a new addition to our Edge Integration Framework.The integration detects known LLM user agents at the edge and redirects eligible requests to a customer-owned Tollbit subdomain, where Tollbit manages authorization, billing, metering, transformation, and optional caching. Non-LLM traffic continues through the standard Arc delivery path with no behavioral change.

This guide outlines the steps necessary to enable Tollbit’s bot monetization solution with Arc XP. 

Below is a step-by-step implementation guide to enable the Arc XP + TollBit Edge Integration.

1) Create Tollbit Account

Make sure your Tollbit account is created, and basic steps (site, domain, billing) completed on our account.

2) Request CDN log forwarding to Tollbit

Tollbit requires CDN/Edge logs to be processed by Tollbit. Arc XP supports CDN log delivery to various destinations. See CDN log delivery with Arc XP for how to request log forwarding for Tollbit. Note: You can only have one log forwarding destination. If you already forward your CDN logs, you may need to replace that with Tollbit destination.

Submit an ACS ticket to Arc so that a DataStream can be created in Akamai to provide Tollbit the site analytics information necessary to make their reporting fully functional.  Integrations

Once fully enabled, using the steps above, Tollbit’s Dashboard provides a list of analytics, insights and configuration controls.

The Tollbit Dashboard also provides the ability to Allow or Block Bots.  Remember, if you provide a list of allowed Bots in Arc it will override any selections in Tollbit.  If you want to manage bot access directly in Tollbit make your sections in their UI and leave the override list blank in Arc.  

3) DNS / Edge hostname setup (per site)

For each site,

1. Create the subdomain:

  • tollbit.site1.com 

  • tollbit.site2.com 

  • tollbit.site3.com 

2. Add the CNAME record(s) pointing to the TollBit-provided target (TollBit will give you the exact hostname).

  • Example format :

    tollbit.<site> CNAME <tollbit-target-hostname> 

3. Verify property ownership through DNS verification:

  • Once you create a property, we need to verify your ownership of the domain before we can continue with your TollBit integration. Verifying a Property

4. Confirm propagation:

  • DNS resolves correctly

  • TLS/cert is valid (your CDN/edge stack may need SAN coverage depending on how hostnames are managed)

Note: The Arc edge integration forwards LLM traffic to tollbit.yoursite.com, so the hostname must work before you turn on the integration. If the domains are not configured before turning the integration on, your LLM traffic may end in non-configured domain, and may get 404s. 

4) Configure the Tollbit Edge Integration in Arc Delivery UI (per site)

Repeat these steps for each site in the desired Arc environment (Prod, Staging, etc).

  1. Open Delivery UI in Arc XP Admin.

  2. Select View for the site you wish to configure and then go to Edge Integrations tab.

  3. Scroll down to the Tollbit integration and enable the toggle on the right hand side.

  4. Should you wish to override the list of enabled/disabled bots configured directly in Tollbit you can provide a comma delimited override list in the Arc UI. 

Once you turn the edge integration on, your LLM traffic will be redirected to tollbit subdomain of the same site, which Tollbit will be handling that request and appropriately respond to LLMs if they need to pay to access to that content with your license configuration in Tollbit.

In this section: