Skip to content

docs: clarify TinyFish key and route eligibility - #125

Open
dorukardahan wants to merge 1 commit into
mainfrom
fix/issue-124-tinyfish-routing-docs
Open

dorukardahan wants to merge 1 commit into
mainfrom
fix/issue-124-tinyfish-routing-docs

Conversation

@dorukardahan

Copy link
Copy Markdown
Owner

Summary

  • clarify that TINYFISH_API_KEY enables provider status and live Search + Fetch contract benchmarking
  • distinguish explicit route planning from automatic runtime route eligibility
  • link the Quick start wording to the detailed provider guidance

No runtime routing or configuration behavior changes.

Verification

  • go test ./internal/core ./internal/cli
  • bash scripts/audit.sh --ci
  • go test -race ./...
  • ./scripts/check-release-builds.sh
  • ./scripts/secret-scan.sh

Closes #124

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify TinyFish key presence versus route selection

1 participant