Skip to content
Good for Bots

AI voice agents that answer and make business calls

Good for Bots: Fair, 49 of 100Get this badge →

On your homepage, it turns this report’s link to pulastya.sdlccorp.com dofollow.

Scanned

What is Pulastya AI?

Pulastya AI is a platform that allows businesses to automate inbound and outbound phone calls using AI voice agents. Designed for use cases such as customer support, healthcare, e-commerce, banking, real estate, hospitality, and education, the product offers configurable voice providers, knowledge integration through uploaded PDF documents, prompt templates, and a call dashboard. It features browser-based testing, full call transcripts, sentiment analysis, and human handoff capabilities that transfer calls to team members when necessary.

Through a bot’s eyes

“Pulastya AI is a platform for building AI voice agents that handle inbound and outbound business calls using your documents, custom instructions, and telephony providers.”

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

The text covers the features, workflows, technology integrations, and industry use cases of Pulastya AI. It details how agents connect via Twilio or Exotel, utilize text-to-speech providers like OpenAI, ElevenLabs, Amazon Polly, or Google, and reference uploaded PDF documents to answer caller queries. The content explains the workspace dashboard, call logging, transcripts, sentiment tracking, and browser testing. Pricing figures are absent, with instructions to contact the team for cost details. Contact information is provided via demo booking links. The embedded JSON-LD blocks provide structured organization data, a software application description, and a frequently asked questions section that reinforces the details found on the homepage.

What stays hidden

Specific numeric pricing details and self-serve checkout options are missing from the input, as pricing requires contacting the team. Exact technical setup documentation and API specification references are also not included in the text.

Good for Bots report

Pulastya AI scores 49 of 100: 49 of the 50 base points, none of the agent layer, no penalties.

Earned

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

49

Still open

Behind the checks below, with prompts in Pro.

17
Penalties0
How scoring works · current methodology →

For the owner of pulastya.sdlccorp.com

3 prompts, 34 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

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

Readable base

49.1 / 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 9 URLs.

Passes.

8.8 of 8.8 points.

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

Passes.

10.5 of 10.5 points.

All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.

Passes.

8.8 of 8.8 points.

18 of 18 assessed homepage navigation links expose usable destinations.

Passes.

4.4 of 4.4 points.

67 of 67 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.

Passes.

2.6 of 2.6 points.

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

Half passes.

0.9 of 1.8 points.

1 of 4 pages read pass; 3 partly. The page at /ai-call-center-automation names the homepage as its canonical URL, which claims the two carry the same content.

Prompt in Pro →

Agent layer

0 / 50

Fails.

0 of 11.3 points.

/llms.txt returns an HTML page rather than markdown.

Fails.

0 of 7.5 points.

No usable /llms.txt to judge.

Prompt in Pro →
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.

Prompt in Pro →
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 2056 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 321 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.

/.well-known/api-catalog answers with a web page, the way a site answers a path it does not implement, so no API catalog is established.

Not applicable.

Adds +1 to the badge when found.

/auth.md returns an HTML page rather than a markdown document.

Not applicable.

Adds +1 to the badge when found.

/.well-known/ai-catalog.json returns an HTML page rather than an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

/.well-known/agent-card.json returns an HTML page rather than an A2A Agent Card.

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.

/.well-known/http-message-signatures-directory returns an HTML page rather than a key directory.

Not applicable.

Adds +1 to the badge when found.

/.well-known/x402 returns an HTML page rather than an x402 manifest, and no 402 payment challenge was seen.

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.

Site profile

Login
Not established
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.

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://pulastya.sdlccorp.com/

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

Sources and scope: declared crawling rules
  • 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://pulastya.sdlccorp.com/

    robots.txt is present and valid

  • Declared allow · robots.txt

    • goodforbotsbot (Site diagnostics)
    • * (Default robots group)
    • oai-searchbot (ai-search)
    • claude-searchbot (ai-search)
    • perplexitybot (ai-search)
    • mistralai-index (ai-search)
    • kimi-searchbot (ai-search)
    • amzn-searchbot (ai-search)
    • meta-webindexer (ai-search)
    • exasearchbot (ai-search)
    • aiwebindex (ai-search)
    • duckassistbot (ai-search)
    • shapbot (ai-search)
    • yandexadditional (ai-search)
    • yandexadditionalbot (ai-search)
    • gptbot (ai-training)
    • claudebot (ai-training)
    • mistralai-training (ai-training)
    • kimibot (ai-training)
    • ai2bot (Unknown)
    • applebot-extended (ai-training)
    • webzio-extended (ai-training)
    • chatgpt-user (user-fetch)
    • claude-user (user-fetch)
    • perplexity-user (user-fetch)
    • mistralai-user (user-fetch)
    • kimi-user (user-fetch)
    • amzn-user (user-fetch)
    • diffbot-user (user-fetch)
    • firecrawlagent (extraction)
    • webzio (extraction)
    • meta-externalfetcher (user-fetch, agent)
    • google-extended (ai-training, grounding)
    • meta-externalagent (ai-training, product-improvement)
    • amazonbot (ai-training, product-improvement)
    • ccbot (open-dataset, ai-training)
    • googlebot (search)
    • bingbot (search)

    No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.

    Acquisition of https://pulastya.sdlccorp.com/

    https://pulastya.sdlccorp.com/robots.txt

    User-agent: *
    allow: /

    robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
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

48th of 60 in AI Products & Agents

  1. 1Pixelropepixelrope.com
  2. 2Contents Pilotcontentspilot.com
  3. 48Pulastya AI · this reportpulastya.sdlccorp.com

The prompts in the owner view would take Pulastya AI to 83, 9th in its category.

To the prompts →

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

Scan details

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

Scanned
30 Oct 2026
Rubric
0.9.0
Requests
23
Fetched
1.9 MB
Took
18.2 s
Homepage
321 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
  • /ai-call-center-automationfrom the sitemap · read
  • /ai-calling-agentfrom the sitemap · read
  • /banking-ai-callingfrom the sitemap · read

Do you run pulastya.sdlccorp.com? Open the owner view → Removing the listing is free. Remove →