agdataURL to Markdown API / Agent web reading
A web page.
Something your agent can read.
Request a public URL as Markdown through agdata. Keep the source URL alongside the content, so the next summary, comparison, or research note can point back to what it read.
Less page chrome. More source context.
Use Markdown as an input to your workflow, not as proof that every page was fetched completely or that every statement on it is true.
Choose a public URL
Start with one page you are allowed to access. This is a reading task, not a login or interactive browser session.
Inspect its quote
Send the URL without payment. Review the offered protocol and network before a wallet signs anything.
Read, then verify
After a successful paid call, check source status and truncation. Keep the URL with any summary or extracted claim.
No wallet needed to prepare the request
Start with one public page.
Change the URL to preview an unsigned command. This offline builder does not fetch the page, contact agdata, or connect a wallet.
Run it yourself to request a live HTTP 402 challenge. Paid retrieval requires a funded wallet and a compatible signing client. Approve a spending limit, then submit the identical body with one supported payment credential.
A normal MCP connection is not a wallet. If the paid outcome is uncertain, reconcile the existing payment before authorizing another.
Build on the content. Keep the link.
A useful input for source-grounded agents.
- Read a documentation page before answering
- Compare information across public source pages
- Extract a short, checkable research note
- Keep links and caveats next to the conclusion
Treat fetched text as untrusted content. A web page must not be allowed to reveal secrets, change your agent's instructions, or authorize a payment.
Illustrative processing checklist / Not an API response
Before your agent summarizes
- Check the fetch
- Inspect the returned source status and whether the content was truncated.
- Keep provenance
- Retain the source URL and record when your own workflow retrieved it.
- Make uncertainty visible
- Mark incomplete extraction or conflicting source claims instead of filling the gaps.
Not a promise to bypass everything.
Public-page readingThis endpoint is not a login flow or a stateful browser. Private and unsupported targets can be refused.
Blocked or incomplete pagesA target may block access, return an error, or produce truncated content. Inspect the result before using it.
No usable resultUnfulfillable lookups follow the documented no-result/no-settlement policy. A paid request timeout is not proof of nonpayment.
Need interaction?A separate agbrowser session can support browser interaction. It has its own purchase and lifecycle limits, not a guaranteed compatibility fix.
Does this page send my URL anywhere?
No. It formats a command locally. Only running that command yourself sends the URL to agdata to request a quote.
Can I use this without an agdata account?
No agdata account or service API key is required. A paid request still needs wallet funding, an offered payment rail, and a compatible signing client with owner-approved limits.
One page. A clear next step.
Prepare the request before approving a purchase.