50/50 RevShare Integration: OpenHands & AIML API

Is there an existing feature request for this?

• I have searched existing issues and feature requests, and this is not a duplicate.

Problem or Use Case

Hi! I'm Hugo from aimlapi.com — an AI aggregator that gives access to 1000+ models in one API, trusted by 400k+ users.

Since LiteLLM (and therefore the OpenHands SDK) already routes to us as the aiml provider, we completed the integration on the OpenHands side: AIMLAPI is now registered as a verified provider with a curated list of flagship tool-calling models, so it shows up in the agent-server catalog and the Agent Canvas provider picker like the other verified providers, and aiml-routed calls carry OpenHands partner attribution the same way OpenRouter calls already do.

To build our partnership, we offer a 50/50 revenue share on all traffic from this integration. (P.S.: tracking starts as soon as this release goes live, so no earnings will be lost during setup)

The problem today: AIMLAPI already works through LiteLLM's aiml provider, but the SDK doesn't list it as verified. So in Agent Canvas it lands in "Other" with an unfiltered dump of model ids, and users have to guess which ones work with the agent. And unlike OpenRouter, requests sent through aiml carry no attribution, so we can't tell OpenHands traffic from anyone else's.

Desired Behavior

• AIMLAPI shows up as a verified provider with a short list of flagship models (Claude, GPT, Gemini, Grok, DeepSeek, Qwen, GLM, Kimi, MiniMax), same as the other verified providers.
• Requests routed through aiml carry two attribution headers (X-AIMLAPI-Partner-ID, X-AIMLAPI-Source), added the same way OpenRouter's HTTP-Referer / X-Title are added today. Other providers are untouched.
• Nothing else changes: model ids stay aiml/<model>, no new base URL or env var.

Acceptance Criteria

• aiml appears in VERIFIED_MODELS and in GET /api/llm/models/verified
• Verified aiml models don't show up again in the "unverified" list
• Calls to aiml/... models carry the two attribution headers; calls to any other provider don't
• Unit tests cover the above

Alternatives Considered

No response

Priority / Severity

Medium - Would improve experience

Estimated Scope

Small - API addition, config option, or minor change

Feature Area

• Agent API / Core functionality
• Tools / Tool system
• Skills / Plugins
• Agent Server
• Workspace management
• Configuration / Settings
• Examples / Templates
• Documentation
• Testing / Development tools
• Performance / Optimization
• Integrations (GitHub, APIs, etc.)
• Other

Technical Implementation Ideas (Optional)

No response

Additional Context

No response

Start by locating VERIFIED_MODELS and the implementation behind GET /api/llm/models/verified, then find how OpenRouter adds attribution headers. Add the verified aiml models and provider-specific headers without changing other providers, and run the relevant unit tests covering verified-model filtering and request headers.