Contributing Your Own Vendor Key to the Aggregator: From Handing It Over to Seeing USDC Accrue

What a contributed key is (and isn't)

A contributed key is an API key from a model vendor that you own and hand over to the aggregator's shared pool. Once accepted, the aggregator may use that key to serve requests from other users. You are not selling the key outright; you are making its capacity available and earning USDC credit when it is used.

Key points:

• The key remains associated with your vendor account. You are responsible for its validity and for complying with the vendor's terms.
• The aggregator routes calls through the shared pool. Your key may serve any eligible request, not just your own.
• You can typically revoke a contributed key at any time from your dashboard. Revocation stops future accrual but does not erase credit already earned.

Why contribute a key?

Contributing a key turns spare vendor capacity into USDC credit that offsets your own API spend on the aggregator. The economics are transparent:

• Regular users pay official vendor price × 1.3.
• Contributors are credited official vendor price × 1.1 (or × 1.2 for premium models) in USDC for calls served by their key.

So if your key serves a call that would cost X at official pricing, you earn 1.1X (or 1.2X for premium) in credit, while the caller pays 1.3X. The difference covers the aggregator's routing, billing, and settlement costs.

How return USDC accrues per call

Accrual is per call, not per key or per day. When a request is routed through your contributed key, the aggregator records the official price for that call, applies the contributor multiplier (×1.1 or ×1.2 for premium), and adds the result to your contributor balance.

What you should expect to see:

• A line item for each served call, showing the model, token counts, official price, and your credited amount.
• A running contributor balance denominated in USDC.
• Periodic settlement or withdrawal options, depending on the platform's payout schedule.

Accrual is tied to actual usage. If your key is idle, no credit accrues. If a call fails or is refunded to the caller, it typically does not generate contributor credit.

Reconciling earned credit against your own spend

Your account can be both a contributor and a consumer. The dashboard should present both sides clearly so you can reconcile them.

A simple reconciliation workflow:

1. Export or review your contributor ledger. Filter by date range and sum the credited amounts per model.
2. Export or review your own call spend. This is what you paid as a user, already including the ×1.3 multiplier.
3. Compare the two totals. Contributor credit is in USDC; your spend is also in USDC on the same account. The difference is your net position for the period.
4. Check for premium multipliers. Calls served by premium models earn ×1.2 instead of ×1.1. Make sure your ledger reflects the correct multiplier.
5. Reconcile any discrepancies. If a call appears in your spend but not in your contributor ledger (or vice versa), check whether it was routed through the shared pool or served directly by the vendor.

Because both sides are denominated in USDC, you can net them directly. For example, if you earned C USDC in contributor credit and spent S USDC on your own calls during the same period, your net cost is S − C. This is a cash-flow view, not a claim about effective discount rates.

Practical tips

• Start with one key. Contribute a single key, observe accrual for a billing cycle, then scale up if the economics work for you.
• Monitor vendor limits. Your vendor account's own quotas and rate limits still apply. Contributing a key does not increase them.
• Keep keys healthy. Rotate or revoke keys that are compromised or no longer used. A revoked key stops accruing immediately.
• Use the ledger, not estimates. The contributor ledger is the source of truth for earned credit. Estimates based on token counts can drift from actual billed amounts.
• Separate personal and contributed usage mentally. Your own calls are billed at ×1.3; contributed calls earn ×1.1 or ×1.2. Mixing the two without a ledger makes reconciliation harder.

Common questions

Does contributing a key change what I pay for my own calls?
No. Your own calls are still billed at official price × 1.3. Contributor credit is separate and accrues only when your key serves someone else's call.

Can I contribute multiple keys?
Yes, typically. Each key is tracked separately in the ledger so you can see which keys are earning.

What happens if my key is rate-limited or suspended by the vendor?
Calls routed to it will fail or be rerouted, and no credit accrues for failed calls. Keep your vendor account in good standing.

Is contributor credit withdrawable?
Payout options depend on the platform. Check the dashboard for settlement and withdrawal details.

Summary

Contributing a vendor key is a straightforward way to offset your own API spend with USDC credit. The key is used by the shared pool, credit accrues per served call at official price × 1.1 (or × 1.2 for premium), and you reconcile earnings against your own ×1.3 spend using the contributor ledger. Start small, watch the ledger, and scale only when the numbers make sense for you.