Content

Content represents the actual payload and data that you are looking for as a developer. You get content by making a request to a specific webpage. Every webpage has its own rate.

Response

Name
content
Type
object
Description
Object containing the different sections of the page.
Name
metadata
Type
string
Description
Additional information not within the page that may provide additional contextual information. May include follow up links or topics to suggest to the end user to explore.

Content

Name
header
Type
string
Description
The header of the page. This contains information such as navigation links and other auxillary information not strictly related to the main purpose of the page.
Name
main
Type
object
Description
The main content of the page, excluding any headers, navigational components, or footers, rendered in markdown for easy parsing.
Name
footer
Type
string
Description
The footer of the page. This contains information such as follow up articles, terms of service, and social media links.

Get Content

You should be able to fetch the contents of the page by simply calling tollbit for the page you want to fetch. The call follows the format:

https://gateway.tollbit.com/dev/v1/content/'URL'

This is an example for fetching content from the following URL: https://pioneervalleygazette.com/dragon: https://gateway.tollbit.com/dev/v1/content/https://pioneervalleygazette.com/dragon

The following headers must also be passed in when calling TollBit:

Name
TollbitOrgCuid
Type
string
Description
Account identifier that can be found in the access page of the dashboard.
Name
TollbitToken
Type
string
Description
The generated token used to access data one time.
Name
User-Agent
Type
string
Description
Unique AgentID string for who is allowed to access the page. Make sure to use the AgentID that you will use within your application.

Should your token be valid, you will get the content back, and a transaction that you access this content will be logged on our side. Note that right now the content comes back in markdown, but this is subject to change in the future.

Here is what a standard response would look like:

Response

    {
        "content": {
            "header": "...",
            "main": "December 10, 2023

              Up until now, the internet has successfully differentiated humans and bots (at least enough to rely on). But in the age of AI this will not work. Captchas are easily bypassed, and eventually
              any user interaction on the internet will probably be navigable by an AI agent. Given this future, why continue to distinguish the two? What were to happen if you opened up the
              flood gates to bot mania? Imo, it might actually work to build a newer, more efficient layer of the internet where you dont have to actually navigate page to page. Instead all
              a human needs to do is ask for exactly what they want.

              When you think about what you do daily on the internet today you probalu think about scrolling on TikTok, X, or checking your email.

              Obviously, there are many concerns with such a drastic change to the internet.",
            "footer": "..."
        },
        "metadata": "...",
        "rate": {
            "priceMicros": 20000,
            "currency": "USD",
            "licenseType": "ON_DEMAND_LICENSE",
            "licensePath": "...",
            "error": ""
        }
    }