Skip to content

Feature Proposal: API for Programmatic Proxy Access #1

@oyi77

Description

@oyi77

Feature Proposal: API for Programmatic Proxy Access

Summary

Project: OmniRoute - A unified AI proxy/router with 100+ providers

Proposal: Add a public API endpoint in 1proxy to allow programmatic access to the validated proxy list, enabling integration with OmniRoute's proxy infrastructure.

Motivation

OmniRoute currently has comprehensive proxy management capabilities:

  • Proxy registry with CRUD operations
  • Scope-based assignments (global, provider, account, combo)
  • Proxy health monitoring
  • MITM proxy capability

However, users currently need to manually configure proxies. Integrating with 1proxy would:

  1. Provide automatic access to free, validated proxies
  2. Enable proxy rotation for improved reliability
  3. Add quality-based proxy selection (using 1proxy's 0-100 scoring)

Proposed Implementation

Option 1: Open API Endpoints (Preferred)

Expose existing internal API for public access:

GET /api/v1/proxies          - List all proxies with filters
GET /api/v1/proxies/random   - Get random proxy with filters
GET /api/v1/proxies/export   - Export in TXT/JSON/CSV format

Filter parameters:

  • protocol: http, socks4, socks5
  • country: Country code (US, GB, etc.)
  • anonymity: transparent, anonymous, elite
  • min_quality: Minimum quality score (0-100)
  • limit: Maximum number of proxies to return

Option 2: GitHub RAW File URLs

Continue providing RAW file access to proxy lists:

  • Document stable URLs for programmatic access
  • Add JSON format for easier parsing

Option 3: RSS/Webhook

Notify registered services when proxy list updates.

Benefits for 1proxy

  1. Increased Usage: Integration with OmniRoute (1000+ users) drives traffic
  2. Community Engagement: Shows 1proxy is integration-friendly
  3. Feedback Loop: Integration reports help improve proxy quality

Request Details

For Option 1, we'd need:

  1. Base URL for the API (e.g., https://1proxy-api.aitradepulse.com)
  2. Rate limits (we'll implement caching to minimize impact)
  3. Documentation for response format

Alternative: OmniRoute as Contributor

If API access isn't feasible, we're happy to contribute:

  1. Documentation improvements
  2. Additional export formats
  3. Webhook/RSS implementation

Next Steps

  1. Confirm which option is feasible
  2. Provide API details or documentation
  3. Test integration
  4. Announce in both communities

Contact: OmniRoute team via GitHub issues
Timeline: Ready to implement once API details are available

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions