relp.ngo
success
Claude Code
intent

What does relp.ngo do and who is it for? Explain it back to me.

8steps
46.9sduration
$0.5637cost
30,030tokens
15 steps7 reasoning steps4 searches
home
home
search
/mission
/field-work
search
search
search
0%
answer from your site
0%
answer efficiency
33%
followed site links
answer sources
  • from search results80%
  • from agent knowledge20%
url discovery
  • given in the task25%
  • followed a link25%
  • found via web search50%
insight

The agent successfully assembled a comprehensive explanation of RELP's mission, clients, and business model by relying entirely on web search results, after the site itself blocked direct access. The site was not agent-navigable via fetch, requiring the agent to reconstruct the narrative from public announcements and external sources.

  • ›The target domain (relp.ngo) returned HTTP 429 and 403 errors on all direct fetch attempts, forcing the agent to pivot entirely to web search—a heavy friction point that required non-standard navigation.
  • ›Search results included snippets and URLs from the site itself (homepage, mission, news pages, fieldwork), meaning the agent could cite official RELP pages as sources despite never successfully fetching them directly; this worked because search indexers could access the content that the agent's fetch tool could not.
  • ›The agent successfully synthesized a multi-part answer (what, who, pricing, differentiation) from fragmented search results across 4 search queries, demonstrating ability to construct a coherent narrative despite no single fetch delivering complete information.
  • ›Key factual claims—founding team history (RenovAr Argentina), funding model (philanthropy-only), geographic footprint (Jamaica, Barbados, Pakistan, etc.), and service model (free, government-embedded)—all came from search results, not direct page content, leaving the answer vulnerable to indexer staleness.
  • ›The 'What I Couldn't Find' section acknowledged gaps in service scope, engagement lifecycle, and platform details—honest admission that depth information was unavailable, suggesting the site may not publish detailed operational specs publicly or they remained blocked.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →