Skip to content
Good for Bots

Transactional email API for sending app emails from your own domain

Click badge to copy

Changed your site? Run a new scan.

Claim to rescan

Claiming is free. Verify ownership to request a rescan after deploying your changes.

Unclaimed listings are checked automatically every 90 days.

Good for Bots report

Sendaro scores 67 of 100: 49 of the 50 base points, 19 of the 50 agent-layer points, no penalties.

Earned

49 of the 50 base points above the line, 19 of the 50 agent-layer points below it.

67

3 prompts away

Copy them below ↓

28

Taken back

Earned, then taken back by penalties.

1

Still open

Behind the checks below, with prompts in Pro.

4
Penalties0
How scoring works · current methodology →

Through a bot’s eyes

“Sendaro is a transactional email API for developers, used to send password resets, receipts and notifications from your own domain with one API call. The Free plan includes 3,000 emails a month.”

Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

A model reading this input learns that Sendaro covers transactional email sending: verifying a domain through DNS records, creating scoped API keys, a code example, the message lifecycle from queued to delivered, sending subdomains, email logs, signed webhooks, metrics, suppression lists and idempotent sends, followed by an FAQ. Pricing is present as text: the Free plan at 3,000 emails a month, Pro from $17 a month for 50,000 emails, and top-ups at $0.79 per 1,000 emails. Links to documentation, the OpenAPI spec and guides appear on the homepage, but their contents are not in the input. The llms.txt file adds a list of documentation, API contract, agent, pricing, security and guide pages. It also states that an accepted request does not mean delivery and that the MCP integration is in private preview. The JSON-LD adds a contact email, GitHub and npm profiles for the organization, and a Free offer priced at 0 USD.

What stays hidden

The company behind Sendaro, its location and its team are not described anywhere in the input. The documentation, security page, pricing comparison and guides linked from the homepage were not read, so the full set of API endpoints and detailed plan limits are not visible. Whether the AI agent features are available for general use is not stated beyond the llms.txt pointer.

What is Sendaro?

Sendaro is a transactional email API for indie developers and small teams. According to the homepage, it is used to send password resets, receipts and notifications from the sender's own domain with one API call, and to see what happened to each message.

Read more →

79 per 1,000 emails. js SDK. The site also lists signed webhooks, idempotency keys, sending subdomains, an email log and a metrics dashboard.

3 prompts, 28 points

For Claude Code, Cursor or Codex. The score moves after the next scan.

+12.5score from 67 to 80

Serve Markdown at its own URL

No /llms-full.txt and no markdown versions linked from llms.txt.

Read prompt

+10score from 80 to 90

Serve Markdown when asked for it

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Read prompt

+5score from 90 to 95

State a position on AI crawlers

robots.txt names no AI crawlers, so every operator has to guess.

Read prompt

Pro

14 more prompts in Pro

Pro shows a prompt for every fix and drafts your llms.txt and robots.txt. It never changes the score.

$9 once, per listingSee Pro

Deployed your fixes? Rescan to update your score →

Ready-made files

Pro drafts these for this site.

Pro

A ready-made llms.txt and robots.txt

Pro drafts both files for Sendaro from its scan, keeps only links and rules our parsers can verify, and hands them over ready to review and publish. It never changes the score.

See Pro

Select a check to see what we found and how it is graded.

Readable base

48.7 / 50

Passes.

3.5 of 3.5 points.

robots.txt is valid, with 1 user-agent group.

Passes.

8.8 of 8.8 points.

Sitemap declared in robots.txt, listing 19 URLs.

Passes.

8.8 of 8.8 points.

All 4 pages read pass. The homepage describes itself to machines as Organization, WebSite, SoftwareApplication in valid schema.org JSON-LD.

Passes.

10.5 of 10.5 points.

3 of 4 pages read pass; 1 partly. The page at /pricing is partly structured: The outline jumps from h1 to h3, which the standard forbids.

Passes.

8.8 of 8.8 points.

19 of 19 assessed homepage navigation links expose usable destinations.

Passes.

4.4 of 4.4 points.

62 of 62 assessed homepage links and buttons have a nonempty accessible name.

Not applicable.

0 of 0 points.

No applicable form fields were observed in the homepage HTML.

Half passes.

1.3 of 2.6 points.

71 of 72 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Prompt in Pro →
Passes.

1.8 of 1.8 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

18.8 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 8 links across 2 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 100% of links.

Fails.

0 of 12.5 points.

No /llms-full.txt and no markdown versions linked from llms.txt.

Fails.

0 of 10 points.

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Fails.

0 of 5 points.

robots.txt names no AI crawlers, so every operator has to guess.

Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Prompt in Pro →

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 956 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 0 redirects.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 264 ms.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Not applicable.

Adds +1 to the badge when found.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

Adds +1 to the badge when found.

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://sendaro.email/

Measured, our crawler
HTTP 200
GoodForBotsBot received HTTP 200 via a direct request.
Search and user-fetch crawlers refused
0 of 20
robots.txt refuses none of them.
Training crawlers refused
0
Refusing training would not change the score.

Crawlers and what robots.txt declares for them

Rules for the sampled URL, read the way RFC 9309 reads them. These are declarations, not access tests.

Crawlers and what robots.txt declares for them on the sampled URL
CrawlerPurposeDeclared accessScore effectRule that applies
Our crawler, measured
GoodForBotsBotGood for BotsSite diagnosticsFetchedHTTP 200, directNot scoredrobots.txt admitted our crawler
Search and AI answers
OAI-SearchBotOpenAIAI searchAllowedNoneNot named; User-agent: * applies
Claude-SearchBotAnthropicAI searchAllowedNoneNot named; User-agent: * applies
PerplexityBotPerplexityAI searchAllowedNoneNot named; User-agent: * applies
GooglebotGoogleSearchAllowedNot scoredNot named; User-agent: * applies
, all allowed
Fetches a person asked for
ChatGPT-UserOpenAIUser fetchAllowedNoneNot named; User-agent: * applies
Claude-UserAnthropicUser fetchAllowedNoneNot named; User-agent: * applies
Perplexity-UserPerplexityUser fetchAllowedNoneNot named; User-agent: * applies
, all allowed
Model training, never scored
GPTBotOpenAIAI trainingAllowedNoneNot named; User-agent: * applies
ClaudeBotAnthropicAI trainingAllowedNoneNot named; User-agent: * applies
Google-ExtendedGoogleAI training, GroundingAllowedNoneNot named; User-agent: * applies
, all allowed
Agents, extraction and others
, all allowed

The robots.txt groups behind this table

User-agent: *
Allow: /

https://sendaro.email/robots.txt

How to read this table

Each row says what robots.txt asks of that crawler. It does not show whether the crawler obeys, or how a firewall treats it. We measured only our own request.

Refusing search or user-fetch crawlers costs points under AI crawler access. Refusing training crawlers costs nothing.

Indexing directives, Content-Signal and AIPREF preferences are in the tabs below.

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://sendaro.email/

    robots.txt is present and valid

  • Observed · Direct request

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    Our request received HTTP 200. A status alone does not identify a WAF.

    Our recorded direct transport attempt; intermediate attempt URLs are not retained

    https://sendaro.email

    HTTP 200

    Serves the homepage over HTTPS with HTTP 200

  • Observed · Final homepage response

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    GoodForBotsBot received HTTP 200 via a direct request.

    homepage response

    https://sendaro.email/

    HTTP 200
    Transport: direct

    Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge

Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

In its category

26th of 57 in Developer Tools & APIs

  1. 1Good for Botsgoodforbots.com
  2. 2ProxyJamproxyjam.com
  3. 26Sendaro · this reportsendaro.email

The prompts above would take Sendaro to 95, 3rd in its category.

To the prompts ↑

Category average 63. The percentile appears once the catalogue holds a few hundred sites.

Scanned

Site profile

Login
Detected
A sign-in or sign-up link
API
Not established
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
10 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
3.4 MB
Took
27.1 s
Homepage
264 ms · direct
Pages read
4
robots.txt
allowed
Which pages the scan read

The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.

  • Homepagealways read
  • /blog/hard-bounce-vs-soft-bouncearticle · from the sitemap · read
  • /pricingpricing · linked from the homepage · from the sitemap · read
  • /docscollection · linked from the homepage · from the sitemap · read

More like Sendaro:Developer Tools & APIsB2BDevelopersFreemium

Same category

volanea.com

Transactional email, campaigns, and automation API with AI agent support

Same category

goodforbots.com

Evaluates website readability for AI crawlers and language models with a scoring rubric

Also Developers

saascubes.com

Curated SaaS directory offering permanent do-follow backlinks for modern software products

Also Developers

dolaai.pro

AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor

Also B2B

vouchgeo.com

Tracks how AI assistants mention a brand across multi-question buying conversations

Also B2B

submityourstartup.now

Free weekly launch directory where early-stage founders list startups and are ranked by votes