Skip to content

Research provider usage access for OpenAI, Anthropic, and Google #3

@cbusillo

Description

@cbusillo

Objective

Identify the reliable and acceptable usage-limit data sources for OpenAI, Anthropic, and Google before implementing provider adapters.

Finish Line

The repo has a documented provider access matrix covering available APIs or account surfaces, auth requirements, terms/risks, refresh limits, data fields, reset semantics, and recommended v1 implementation path for each provider.

Current Status

State: Provider usage access research is documented in PR #8.
Next action: Review the provider matrix and decide whether OpenAI ChatGPT forecasting should be the first implementation slice.
Blocked by: Review of PR #8 and confirmation of acceptable local/manual tracking for ChatGPT accounts.
Last verified: 2026-05-05.

Scope

  • OpenAI usage/limits surfaces.
  • Anthropic usage/limits surfaces.
  • Google/Gemini usage/limits surfaces.
  • Multi-login implications for each provider.
  • Terms-safe and friend-distribution-safe implementation recommendations.

Acceptance Criteria

  • Provider access matrix is committed to docs.
  • Each provider has a recommended v1 approach: official API, manual/API-key configuration, browser-assisted local fetch, or deferred.
  • Risks and unknowns are captured explicitly.
  • Follow-up implementation issues are updated if research changes the architecture.

Relationships

Validation

  • Cite official docs where possible.
  • Avoid relying on stale memory for provider behavior.

Decisions

  • OpenAI API organization usage can use official Usage/Costs APIs and rate-limit headers.
  • ChatGPT personal weekly message allowance does not have a stable public used-count API in the researched docs, so v1 should use local/manual/assisted observations with explicit forecast confidence.
  • Anthropic API usage/cost tracking can use official Usage and Cost APIs plus rate-limit headers.
  • Google API project tracking should use project-scoped quotas, Cloud Monitoring quota metrics, and optional Billing export rather than consumer Gemini app scraping.

Open Questions

  • Can each provider expose usage limits through official APIs for individual users?
  • Which account types are realistic for friends to connect?

Metadata

Metadata

Assignees

No one assigned

    Labels

    planDurable planning issueplan:activeCurrent active plan

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions