Discover/example API
live

example APIexample.com

Fetch the example.com homepage title, headings, paragraphs, hyperlinks, language code, and last-modified date in a single API call.

Endpoint health
verified 7h ago
get_site_info
1/1 passing latest checkself-healing
Endpoints
1
Updated
8h ago

What is the example API?

The example.com API exposes 7 response fields from the example.com homepage in a single call to the get_site_info endpoint. It returns the page title, document language, main heading, all visible paragraph texts in document order, every hyperlink as a structured text-and-URL pair, the final resolved URL, and the HTTP Last-Modified timestamp — making it straightforward to monitor or reference the canonical example domain.

This call costs1 credit / call— charged only on success
Try it

No input parameters required.

api.parse.bot/scraper/146cd725-d4ef-4a67-b229-de9d054987e4/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/146cd725-d4ef-4a67-b229-de9d054987e4/get_site_info' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace example-com-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: example.com site info SDK — fetch and inspect the homepage."""
from parse_apis.example_com_api import ExampleCom, ParseError

client = ExampleCom()

# Fetch the single-page site info in one call.
try:
    info = client.site_info.get()
except ParseError as e:
    print("Could not parse site info:", e.code)
    raise
print(info.title, "|", info.heading)
print("Language:", info.language)
print("Last modified:", info.last_modified)

# Walk the paragraphs returned by the page.
for paragraph in info.paragraphs:
    print("-", paragraph[:120])

# Inspect each outbound link as a typed Link object.
for link in info.links:
    print(link.text, "->", link.url)

print("exercised: site_info.get")
All endpoints · 1 totalmissing one? ·

Fetches the example.com homepage in one round trip and returns its basic information: the page title, document language, main heading, all visible paragraphs in document order, every hyperlink (link text and absolute URL), and the last-modified timestamp reported by the site. Takes no parameters. The site is a single static page, so the result is one object and never paginates; an empty paragraphs or links array only occurs if the page content changes.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "url": "final URL of the fetched page",
    "links": "array of {text, url} objects for each hyperlink on the page",
    "title": "HTML document title",
    "heading": "text of the main h1 heading",
    "language": "document language code from the html lang attribute, or null if absent",
    "paragraphs": "array of visible paragraph texts in document order",
    "last_modified": "HTTP Last-Modified date string reported by the site, or null if not sent"
  },
  "sample": {
    "data": {
      "url": "https://example.com/",
      "links": [
        {
          "url": "https://iana.org/domains/example",
          "text": "Learn more"
        }
      ],
      "title": "Example Domain",
      "heading": "Example Domain",
      "language": "en",
      "paragraphs": [
        "This domain is for use in documentation examples without needing permission. Avoid use in operations.",
        "Learn more"
      ],
      "last_modified": "Tue, 15 Sep 2026 23:41:26 GMT"
    },
    "status": "success"
  }
}

About the example API

What the API Returns

The single get_site_info endpoint requires no input parameters and returns all publicly visible content from the example.com homepage in one response. The title field contains the HTML document title, while heading holds the text of the main <h1> element. The language field surfaces the lang attribute of the <html> tag, or null when the attribute is absent. The paragraphs array delivers all visible paragraph texts in document order, which reflects the page's readable body content.

Links and URL Data

The links field returns an array of objects, each containing a text string (the anchor text) and a url string (the absolute URL). This makes it possible to enumerate every hyperlink on the page without additional parsing. The url field at the top level of the response reflects the final resolved URL after any redirects, so callers can detect canonical URL changes.

Freshness and Metadata

The last_modified field returns the HTTP Last-Modified date string as reported by the server, or null if the header is not present. This gives a lightweight signal for detecting whether the page content has changed since a previous call, without needing to diff the full response body.

Reliability & maintenanceVerified

The example API is a managed, monitored endpoint for example.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when example.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official example.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
7h ago
Latest check
1/1 endpoint passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Monitoring the example.com homepage for changes to its title, heading, or paragraphs content over time.
  • Extracting all hyperlinks via the links array to audit outbound URLs and anchor text on the reference domain.
  • Checking the last_modified timestamp to determine whether the page has been updated since a previous fetch.
  • Verifying the language code reported by the page for internationalization or content-type tooling.
  • Using the url field to detect canonical URL redirects or domain-level changes.
  • Pulling paragraph text for use as placeholder or sample content in UI prototypes and developer tooling.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does example.com have an official developer API?+
No. example.com is a reserved demonstration domain maintained by IANA and provides no official developer API or data feed. This Parse API is the structured way to access its public page data.
What does the `links` field in the get_site_info response include?+
The links field returns an array of objects, each with a text property (the visible anchor text) and a url property (the absolute URL). Every hyperlink present on the page is included; there is no filtering by link type or destination domain.
Does the API return data from pages other than the homepage?+
Not currently. The API covers only the example.com root homepage via get_site_info. You can fork it on Parse and revise it to add endpoints targeting other URLs or subpages.
Can I get structured metadata beyond what is listed, such as meta description or Open Graph tags?+
Not currently. The response includes title, heading, language, paragraphs, links, url, and last_modified. Meta description, Open Graph tags, and other <head> metadata are not exposed. You can fork the API on Parse and revise it to add those fields.
How reliable is the `last_modified` field for detecting content changes?+
The last_modified value is the raw HTTP Last-Modified header string returned by the server, or null if the server omits it. It reflects server-reported freshness, not a diff of the response body, so a null value or an unchanged timestamp does not guarantee the content is identical to a prior fetch.
Page content last updated . Spec covers 1 endpoint from example.com.
Related APIs in Developer ToolsSee all →