{"uid":"cap_-MigNoj6c293FA_dR6f5x","slug":"synthora-ripestat-abuse-contact-finder-4285c39e","name":"SYNTHORA RIPEstat Abuse Contact Finder","description":"Returns the responsible abuse-desk email address(es) for an IP, prefix or ASN, sourced from RIR databases via RIPEstat. A2A use: anti-abuse, takedown and incident-response agents auto-route complaints to the correct network operator without manual WHOIS parsing. First 3 calls FREE per wallet — send header X-WALLET: 0x<addr>. No charge on upstream failure.","url":"https://ripestat-abuse-contact.hergertsynthora.com/service","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"ip":{"type":"string","description":"ip"}}},"responseSchema":{"type":"json","example":{"ok":true,"niche":"ripestat-abuse-contact","result":{"sources":[],"resource":"8.8.8.8","abuse_contacts":[]},"provenance":{"url":"https://stat.ripe.net/data/abuse-contact-finder/data.json?resource=8.8.8.8","source":"RIPEstat Abuse Contact Finder"}}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.001","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.001/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.001","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.001","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_tpf6kAvEhRVvPB0OkbBrZ","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.001","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Looks up the responsible abuse-desk email address(es) for a given IP address, prefix, or ASN using RIPEstat data from RIR databases.","exampleAgentPrompt":"Find the abuse contact email for IP address 185.220.101.45 so I know where to send a takedown complaint.","exampleUseCases":[{"title":"Auto-route spam complaint to operator","prompt":"We've been getting spam from IP 203.0.113.42 — find the abuse contact for that IP so I can send a complaint to the right network operator automatically."},{"title":"Incident response abuse notification","prompt":"We detected a DDoS attack originating from 45.33.32.156. Look up the abuse desk email for that IP so our security team can file a report right away."},{"title":"Bulk IP abuse contact resolution","prompt":"I have a list of IPs flagged for malicious traffic — start with 91.108.4.1 and find its abuse contact so I can route the takedown notice to the correct network team."}],"resultDescription":"Returns a JSON object containing the queried resource (IP/prefix/ASN), a list of abuse contact email addresses associated with that network, and provenance metadata including the source RIPEstat API URL used to retrieve the data.","failureModes":["No abuse contact found — returns empty abuse_contacts array for IPs/ASNs with no registered abuse address in RIR databases","Invalid IP or ASN format — malformed input may return an error or empty result","RIPEstat upstream unavailability — if RIPE NCC's API is down, the service may fail or return stale data","Private/reserved IP ranges (e.g. RFC1918) will return no meaningful abuse contact","Rate limiting or payment failure if USDC micropayment is not processed correctly"],"whenToPreferThis":"Use this endpoint when you need to programmatically resolve the correct abuse-desk contact for an IP, prefix, or ASN without manually parsing WHOIS output. It is ideal for anti-abuse pipelines, automated takedown workflows, and incident-response agents that must route complaints to the correct network operator. Prefer this over raw WHOIS lookups when you need a clean, structured JSON response with extracted abuse emails rather than free-text WHOIS data.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-14T18:35:44.325Z","isFirstParty":false}