Abuse/Reputation API
Paid Base USDC reputation signals for IP addresses, email addresses, and combined identity abuse prevention.
1 of 3 routes settlement-verified · $0.00001 USDC/request · 3 endpoints / 3 tools · Intelligence · base network · x402 protocol
Verified routes
POST /v1/ip· $0.00001 · Verified with a $0.000001 test payment on 20 Sep 2026 · receipt
Other routes are unverified.
Networks: Base (settlement-verified)
Discovery is free. Agents search the catalogue here. Payment happens on the listing 402, not on PayAPI.
url https://payapi.market/mcpListing facts
- Provider
- Forum Fortress
- Hosted at
x402.ffapi.net- Category
- Intelligence
- Price
- $0.00001 USDC per request
- Endpoints
- 3
- MCP tools
- 3
- Payment networks
- Base
- Settlement-verified
- 1 route, last checked 2026-09-20
- Listed on PayAPI Market
- 2026-09-20
Try Abuse/Reputation API
Call a verified route without paying first. The server should answer HTTP 402 Payment Required with the price, the USDC asset, the network and the wallet to pay. An x402 client pays that amount on Base and retries with the payment header.
curl -i -X POST "https://x402.ffapi.net/v1/ip"About this API
Abuse/Reputation API is listed in the Intelligence category with pricing at $0.00001 USDC/request. One route has been settlement-verified by PayAPI Market on 2026-09-20. View receipt on Basescan.
Payments settle on base in USDC via the x402 protocol. AI agents discover this API through the PayAPI Market MCP server and pay per request without API keys or accounts.
This API exposes 3 endpoints. Only the verified route has been tested by PayAPI Market. Other routes are unverified.
Add this badge to your README
Paste this on your site. The link points at this listing. Listing is free and providers keep 100%.
Markdown
[](https://payapi.market/api/abuse-reputation-api)
HTML
<a href="https://payapi.market/api/abuse-reputation-api"><img src="https://payapi.market/badge/abuse-reputation-api.svg" alt="Settlement-verified on PayAPI Market" height="20"></a>
Questions about this API
What does Abuse/Reputation API do?
Paid Base USDC reputation signals for IP addresses, email addresses, and combined identity abuse prevention. It is provided by Forum Fortress.
How much does Abuse/Reputation API cost?
Abuse/Reputation API is priced at $0.00001 USDC per request, paid per call with no subscription. Verified with a $0.000001 test payment on 20 Sep 2026. The exact amount for each call is in the HTTP 402 response before any money moves.
Do I need an API key or account to use Abuse/Reputation API?
No. Abuse/Reputation API uses the x402 protocol, so an agent pays per request in USDC on Base and gets the response, with no API key, account or signup.
Has Abuse/Reputation API been verified?
Yes, 1 route of its 3 endpoints. PayAPI Market paid for a real call from its own wallet, received real data back and recorded the USDC settlement on-chain, most recently on 2026-09-20. Routes that were not paid for are unverified.
How does an AI agent find Abuse/Reputation API?
Through the free PayAPI Market MCP server at https://payapi.market/mcp, using search_apis or get_api, or over plain HTTP at https://payapi.market/agent/search. Discovery is free; the agent pays the provider directly on the listing's own 402.
More Intelligence APIs · Browse the marketplace · List your own API
Related APIs
- LLM inference and AI chat over x402: OpenAI-compatible chat completion for $0 · 1 route verified · LLM inference and AI chat over x402: OpenAI-compatible chat completion for $0.002: gpt-oss-120b by default, or gpt-oss-20b, llama-3.3-70b, llama-3.1-8b, qwen3-30b. POST {model, messages}; up to 1,024 output tokens, tools supported, no streaming. OpenAI-compatible chat completion (gpt-oss-120b default; gpt-oss-20b, llama-3.3-70b, llama-3.1-8b, qwen3-30b). POST {model, messages, max_tokens<=1024}.
- Domain Agent Discovery Check · 1 route verified · Inspect public domains across DNS, HTTP/TLS, email posture and AI-agent discovery surfaces including robots.txt, llms.txt, OpenAPI, MCP, x402 and Agent Cards. Returns issues and readiness signals.
- Sense by QuorumzOne story, the viewpoints being expressed, and the posts supporting each · 1 of 4 routes verified · One story, the viewpoints being expressed, and the posts supporting each viewpoint.Verified, geolocated world events for agents. A quorum gathers every report of one story with place, time, viewpoints
- Live biomedical compound intelligence combining openFDA FAERS adverse-event · 1 route verified · Live biomedical compound intelligence combining openFDA FAERS adverse-event counts & label warnings, ClinicalTrials.gov API v2 trial pipelines, and ChEMBL molecule properties in one structured JSON call.
- Unique request identifiers for agents · 1 route verified · Unique request identifiers for agents. Use when an agent needs a collision-resistant ID for tasks, orders or idempotency keys without importing a library.
- Web page reader for agents: GET /read · 1 route verified · Web page reader for agents: GET /read?url=<public http(s) URL> returns the page as ready-to-use text - title, paragraph blocks, word count - with script, style, noscript, svg, iframe and all markup removed and a fixed 12,000-character cap reported honestly in `truncated`. What makes it worth paying for instead of fetching it yourself: the same deterministic Indonesian entity dictionary and sentiment lexicon behind /feed and /sentiment run on the extracted text (score plus the matched terms, no LLM, no invented number - a page the lexicon cannot read returns sentiment null with the reason in source_note). Safety is part of the product: the hostname is resolved by us and refused if ANY A/AAAA answer is loopback, RFC1918, CGNAT, link-local, cloud-metadata or reserved; the connection then goes to that validated IP with the name used only as SNI and Host, so DNS rebinding has no second lookup to exploit; redirects are never followed (3xx comes back as redirect_blocked plus the Location); the body is cut at 1.5 MB and refused above 2 MB; only text/html, text/plain, text/markdown, application/json and application/xml are parsed; no inbound header is forwarded and nothing is stored. $0.05 USDC per call via x402 or MPP, no signup, no API key.