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) Prerequisites checklist

  • Tollbit:You have created a Tollbit account with Tollbit

  • Arc XP: Submit an ACS ticket to request the tollbit subdomain creation for EACH SITE where you would like the integration.  ACS Ticket Example:

Org: Your Org name

Sites: examplesite1, examplesite2

Environment: Prod

Change type: Add

Sample %: 100

Push frequency: 30 sec

Integration type: Direct feed from CDN → TollBit

  • A TollBit subdomain must exist for each site and is correctly configured via CNAME.

  • Arc will also need a Tollbit provided API key.  This key should be submitted to Arc via secure methods.

2) DNS / Edge hostname setup (per site)

For each site 

  1. Create the subdomain:

  • tollbit.site1.com 

  • tollbit.site2.com 

  • tollbit.site3.com 

  1. 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> 

  1. 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

  1. 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.*, so the hostname must work before you flip traffic. 

4) Configure the 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 → Edge Integrations for the site.

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

  3. Scroll down to the Tollbit integration and enable the toggle on the righthand 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. 

5) Sending Analyitics Data to Tollbit

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.  

In this section: