For developers

Check links and messages from your code or your AI agent. It's the same check as the website: free, up to 20 checks a day.

Just adding URLert to your own assistant? Add URLert to your AI assistant

MCP server

https://www.urlert.com/mcp

For AI agents. It signs in with OAuth.

API

https://www.urlert.com/api/v1/

For your code. It takes an API token.


MCP server

Add the address to your MCP client as a remote server. It asks you to sign in to URLert (or make a free account), then works as you. It can't delete a check or your account.

Its tools

  • check_linkChecks one link before you open it or act on it.
  • check_messageChecks the text of a message, and the links in it.
  • check_pageChecks a page from your own view of it, which we don't open.
  • get_resultA check's result by its id.
  • get_guideThe steps for someone who already acted, most urgent first, or one scam guide.
  • report_mistakeTells us a result is wrong.

The API has the same six operations, by the same names.

Reading our site instead? /llms.txt lists our pages. Add .md to any page's address for its Markdown.

API

1. Make a token

Make a free account, then a token: Account, then AI agents, then New API token. It asks you to confirm it's you, and shows the token once.

2. Check a link

Each operation is a POST to its name, with a JSON body. Send the token as a Bearer token.

Request
curl https://www.urlert.com/api/v1/check_link \
  -H "Authorization: Bearer $URLERT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"link": "https://txtag-tolls.icu/pay"}'

It answers at once, with the check's id and "status": "queued".

3. Get the result

A check usually ends within a minute. Call get_result every few seconds, until status is done or failed.

Request
curl https://www.urlert.com/api/v1/get_result \
  -H "Authorization: Bearer $URLERT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"id": "k3m9x2pq"}'
Answer
{
  "id": "k3m9x2pq",
  "status": "done",
  "outcome": "scam",
  "outcome_name": "Scam",
  "asks_for": ["money"],
  "reasons": [
    {"text": "The page says it's TxTag, but the site is txtag-tolls.icu."}
  ],
  …
}

Every field is always there, null when empty. The reference lists them all.

The outcome

outcome is one of six values. You decide what to do. We suggest:

maliciousscam

Stop. Don't open the link, and don't do what the message asks.

riskysuspicious

Ask the person first. Show them the reasons, in our words or yours.

cant_tell

Send more. The whole message, or your agent's own view of the page, with check_page.

nothing_found

Go ahead, with care. It's what we found, not a promise.

Limits

  • 20 checks a day for each account, MCP and API together. get_result, get_guide and report_mistake don't count. The count starts again at 00:00 UTC.
  • Past it, a check fails with 429 and the code daily_limit, or checks_paused when checks from assistants and programs are paused for the day, with a Retry-After header.
  • Errors are application/problem+json: status, code, detail, and errors for the fields at fault.
  • Checks are deleted after 30 days.