50/50 RevShare Integration: AgentScope & AIML API #2557
hugoaimlapi
started this conversation in
Ideas
Replies: 1 comment
|
The implementation PR is now open: #2576 One commit on top of the current |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi! I'm Hugo from aimlapi.com — an AI aggregator that gives access to 1000+ models in one API, trusted by 400k+ users.
aimlapi.com is OpenAI-compatible, so AgentScope can already reach us today — but only by hand-pointing
OpenAIChatModelat a custombase_url. We completed the integration on the AgentScope side: AIMLAPI is registered as a built-in provider following the chat-model checklist in CONTRIBUTING.md (credential class, chat model class, model card YAMLs, both formatter variants, tests and an example script), and aimlapi-routed calls carry AgentScope attribution headers, scoped so they never leave the aimlapi.com origin.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: there is no aimlapi.com entry in the credential picker, the OpenAI formatter advertises OpenAI's input types rather than ours, and requests carry no attribution, so we can't tell AgentScope traffic from anyone else's.
Desired behavior
X-AIMLAPI-Partner-ID,X-AIMLAPI-Source, plusHTTP-Referer/X-Titlenaming AgentScope — the OpenRouter convention). Other providers are untouched.<vendor>/<model>catalog ids, default base URL ishttps://api.aimlapi.com/v1, the key lives inAIMLAPICredential.The PR with the complete implementation is ready and will be linked here as soon as it's opened.
My contacts: hugo@aimlapi.com (email / Slack), Telegram: @hug0the
All reactions