PUBLIC-WEB TOOLS / FOR PEOPLE + AGENTS

Check the web.Keep the
evidence.

Audit a webpage. Compare products. Check a claim. Get structured results with sources you can inspect.

Explore the tools Connect an agent

Defined inputs. Clear findings. Limits stated up front.

Public webpagesStructured resultsInspectable evidenceREST + MCP

01 / THE TOOLKIT

Pick the task.
Get the evidence.

Each tool has a defined job, an input contract and an explicit set of limits. Start with the work you need done.

01 / WEBSITE AUDIT

Find what needs
fixing.

Check one public webpage for rule-based HTML, HTTP, SEO and accessibility issues. Get a ranked list of actions.

YOU GET / Ranked findings, evidence and suggested fixes in the appropriate response mode.
View the audit example
02 / PRODUCT COMPARISON

Compare what
the pages say.

Compare product information from multiple public pages. Inspect the source-backed fields without filling gaps with guesses.

YOU GET / A structured comparison grounded in the supplied public product pages.
View the comparison example
03 / CLAIM CHECK

Put a claim
to the sources.

Evaluate whether the public sources you supply establish a claim. See the supporting evidence and the remaining uncertainty.

YOU GET / An evidence-based assessment, not an unsupported declaration of truth.
View the claim example
Extract product data

A normalised record from a public product page.

Capture a source snapshot

Bounded source text and a content hash for later checks.

Run page checks

Reproducible HTTP, HTML, SEO and accessibility checks.

Public pages only. does not sign in, bypass access controls, run page JavaScript or provide full WCAG certification.

Explore all six tools

02 / THE OUTPUT

An answer you
can inspect.

The finding is the beginning. You also need to know what it rests on—and where its limits are.

  • Find the next action.Website audits rank rule-based findings by severity.
  • Follow the evidence.Request the evidence response mode to inspect supporting source details.
  • Keep the limits in view.Know what was checked before you decide what to trust.
See how a call works
WEBSITE AUDIT / EVIDENCE MODEEXAMPLE ONLY

Give the page a description.

SEO / ILLUSTRATIVE FINDING

No meta description in the sample HTML.

Add a concise description that explains what this page offers. Make it useful to someone deciding whether to visit.

SAMPLE SOURCE EXCERPT<head>
  <title>Example product page</title>
</head>

HTML-only check. This does not assess rendered layout or guarantee a search ranking improvement.

Illustrative fixture—not a live website result. Switching examples makes no API call.

03 / THE PROCESS

Know the scope.
Then make the call.

No open-ended brief. Choose a defined service, inspect the quote and authorise the work.

01

Choose the tool.

Read its input contract and limitations. Supply the public page or sources that fit the task.

02

Review the quote.

Inspect the service quote before authorising paid execution. People and businesses use Stripe; agents can use x402.

03

Inspect the result.

Choose the response mode that suits the job: minimal, standard or evidence. Use the findings with their stated limits.

Small calls, considered billing. Sub-threshold Stripe usage carries forward and aggregates before invoicing. The service quote defines the charge. Review the quote and advertised payment requirements before authorising a paid call.

Billing questions →

04 / FOR AGENTS

Give your agent
a useful next call.

Connect through MCP or REST. Discover the tools, inspect their contracts and request only the output your task needs.

Defined input schemasThree response modesStructured output
View connection guide Inspect the tools
Connection guide / MCP + REST
  1. In an MCP-compatible client, add the endpoint https://found17.com/mcp. Client setup and authentication support vary.
  2. Discover the available tools. For a first call, inspect website_audit and its input schema.
  3. Review the quote and payment challenge. Use a payment-capable client and authorise the paid call explicitly.
  4. For REST, the audit route is POST https://found17.com/v1/website-audit. Send the public URL and required headers according to the API contract.

Reading this guide does not execute a service or authorise a payment.

05 / THE BOUNDARIES

Clear before
you click.

Useful tools have boundaries. Here are the ones worth knowing first.

Is this for people or agents?

Both. People and businesses can explore the service contracts and use the Stripe billing route. Agents can discover and call services through MCP or REST, with payment support where required. Read the service contract and payment requirements before requesting execution.

What does a website audit actually check?

It checks a public page’s HTTP and HTML for rule-based SEO and accessibility issues, then ranks the findings. It does not run JavaScript, inspect visual layout, predict conversion gains or certify full WCAG conformance.

Can it access private pages?

No. Use public HTTP or HTTPS sources. does not sign in or bypass access controls to inspect private content.

How do paid calls work?

Review the service quote before authorising execution. Stripe provides the human and business billing route; x402 provides an agent payment route. Sub-threshold Stripe amounts aggregate before invoicing. This preview performs no service calls or charges.

Does a claim check prove something is true?

It assesses whether the sources you provide establish the claim. That is a bounded evidence check, not a guarantee of universal truth. Review the evidence, uncertainty and limitations before relying on the result.

Pick a task.
Leave with evidence.

Start with a webpage, a product comparison or a claim you need to check.

Explore the tools Connect an agent