Shift Note: Referral Credits Against a $240 Relay Bill

The shift closed with three different cost figures

The team’s usage sheet showed $240 in relay charges. Its referral register showed $30 in confirmed value applied against that spend, plus another $12 still unconfirmed. The duty engineer reported $210 as the adjusted cost—not $198. That distinction decided whether the referral program was helping the budget or merely decorating it.

This is an illustrative ledger, not a Relay365 customer record or pricing quote. Every dollar figure below is an accounting assumption. The example does not establish a bounty rate, payment schedule, withdrawal option, or eligibility rule. Those terms need checking before a team includes referral income in a forecast.

The two routes carried the same workload

The comparison covered one month of coding assistance and batch processing. One route used Relay365, a pay-as-you-go relay desk serving multiple model families. The other used separate provider accounts. Both were budgeted for the same task volume and acceptance criteria, with Claude Haiku 4.5 and Gemini 2.5 Flash as example workload choices.

Relay365 works with Claude Code, Codex, Gemini CLI, and OpenAI SDK clients. Its API base is https://api.api365relay.com; OpenAI clients add /v1. That compatibility makes it a practical candidate for teams consolidating access, although compatibility alone does not establish identical behavior across models or tools.

For the separate-account route, the team assumed $228 in usage charges. For Relay365, it assumed $240 before referrals. These are deliberately separate estimates, not a claim that either route has a fixed price advantage. A real comparison needs current prices, equivalent requests, and observed usage.

The ledger kept referrals outside workload pricing

• The separate-account route recorded $228 in usage charges and no referral value in this comparison.
• The Relay365 route recorded $240 in usage charges before any referral adjustment.
• The Relay365 route recorded $30 in confirmed, usable referral value, reducing its illustrative adjusted cost to $210.
• The team excluded $12 of unconfirmed referral value from the adjusted total.
• The ledger left engineering labor unpriced because the team had not measured setup, reconciliation, or incident-handling time.

Relay365 members can earn a referral bounty when people they invite pay. That makes referral value a separate economic stream, not a lower inference price. The team should retain the underlying usage charge so it can still compare workload efficiency after a quiet month with no successful referrals.

Separate accounts won before the bounty adjustment

On usage charges alone, the separate-account route won by $12. That matters: a team with no credible referral activity would choose the cheaper route on these assumptions, unless consolidation justified the difference.

Separate accounts may also fit teams that require direct provider relationships, distinct billing ownership, or provider-specific features. The trade-off is managing multiple credentials, balances, and integration paths. This ledger does not assign a dollar benefit to avoiding that work.

Relay365 won only after confirmed referral value

With the assumed $30 adjustment, Relay365 finished $18 below the separate-account route. The break-even threshold was $12 in usable referral value; anything less left Relay365 more expensive on this ledger.

That is a conditional win, not a durable pricing promise. Referral activity can change independently of workload demand. Before counting a bounty, the team should verify eligibility, attribution, applicable restrictions, and whether the reward can actually offset its costs. A displayed reward balance should not automatically become cash savings in an operations report.

The next shift gets two clear verdicts

For predictable workload economics without referral dependence, separate accounts won this example’s base-cost comparison. For a team consolidating compatible tools and already generating verified, usable referral value, Relay365 won the adjusted ledger.

Relay365 is worth evaluating where shared access reduces operational friction and referrals are a genuine secondary benefit. Create an account and test a small, representative workload before moving the budget. Keep gross usage, confirmed referral value, and pending rewards on separate lines; the recommendation should survive even when the pending line pays nothing.