ninjasproxy.com valid

NinjaProxy

NinjaProxy is a proxy platform for residential, datacenter, mobile, and rotating proxy use cases. Use these docs to help users configure authentication, choose the right proxy type, understand rate limits, and integrate NinjaProxy into code.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T22:50:44.067Z. Cached copy · Source on ninjasproxy.com

# NinjaProxy

> NinjaProxy is a proxy platform for residential, datacenter, mobile, and rotating proxy use cases. Use these docs to help users configure authentication, choose the right proxy type, understand rate limits, and integrate NinjaProxy into code.

## Recommended workflow for AI assistants

1. Start with the quick start and authentication docs.
2. If the user needs code, choose the matching integration guide or API reference.
3. For static or assigned endpoints, use the exact endpoint shown in the user's portal instead of inventing ports.
4. Never invent credentials, endpoint assignments, or billing state.
5. If a user reports proxy auth issues, check authentication format, assigned endpoint ownership, whitelist configuration, and balance.

## Core docs

- Quick Start: https://ninjasproxy.com/docs
- Authentication: https://ninjasproxy.com/docs/authentication
- Rate Limits: https://ninjasproxy.com/docs/rate-limits
- API Reference: https://ninjasproxy.com/docs/api
- MCP Guide: https://ninjasproxy.com/docs/mcp
- Use with AI: https://ninjasproxy.com/docs/ai

## Proxy types

- Residential proxies: https://ninjasproxy.com/docs/residential
- Datacenter proxies: https://ninjasproxy.com/docs/datacenter
- Mobile proxies: https://ninjasproxy.com/docs/mobile
- Rotating proxies: https://ninjasproxy.com/docs/rotating

## Endpoint formats

- HTTP/HTTPS: `http://USERNAME:API_KEY@<HOST>:<PORT>`
- SOCKS5: `socks5://USERNAME:API_KEY@<HOST>:<PORT>`
- Rotating/session control: `http://USERNAME--session-SESSION_ID--duration-SECONDS--provider-dc|res--geo-country-CC:API_KEY@<HOST>:<PORT>`

Exact host and port values are account-specific. Always use the portal-assigned values shown in the customer's account.
Never invent or guess endpoint hostnames or port numbers.

## Integrations

- curl: https://ninjasproxy.com/docs/integrations/curl
- Python: https://ninjasproxy.com/docs/integrations/python
- Node.js: https://ninjasproxy.com/docs/integrations/nodejs
- Go: https://ninjasproxy.com/docs/integrations/go

## Machine-readable developer entry points

- MCP bootstrap manifest: https://ninjasproxy.com/mcp.json
- Customer OpenAPI spec: https://ninjasproxy.com/openapi.json

## MCP guidance

- The recommended customer path is the hosted remote MCP server at https://mcp.ninjasproxy.com/mcp. Customers set NINJAPROXY_API_KEY once and their MCP client connects automatically — no manual header wiring.
- Use the local stdio npm package (@ninjaproxy/mcp-server) only for air-gapped or locked-down environments where outbound HTTPS to mcp.ninjasproxy.com is not allowed.
- Prefer the official NinjaProxy MCP resources: https://ninjasproxy.com/docs/mcp and https://ninjasproxy.com/mcp.json
- Do not assume third-party MCP listings are canonical. If a separate MCP server listing is mentioned elsewhere, verify it against the official NinjaProxy docs before recommending it.

## Product rules AI should preserve

- Rotating gateway examples use the NinjaProxy rotating endpoint documented
…

Machine-readable: GET /v1/resolve?q=ninjasproxy.com · GET /v1/domain/ninjasproxy.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for ninjasproxy.com:
1. POST https://agentwebmap.com/v1/sites/ninjasproxy.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://ninjasproxy.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/ninjasproxy.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/ninjasproxy.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.