redact-secret · Report

API token

r8_ prefixed API token; the provider documents a 40-character total (a 37-character body) and does not state the body alphabet.

Replicate
Detectors: replicate-api-token
Run 2026-10-07
Mode published · redact-secret 0.1.0-beta.14

All providers

Dossier verdictReady
Dossier evidence levelT1 · Provider-documented
Dossier researched2026-09-24

Registry detector replicate-api-token since redact-secret#727 (registry pinned at dad7868); graduated from a Beta.8 arrival family (#208, research #217), contract in benchmarks/lib/beta8/208.ts. The body alphabet is peer-contested (TruffleHog admits - and _; flare-redact alphanumeric only) and stays provisional. The cog/r8.im login token's relation to this token is undocumented and not claimed.

New pipelineAuthority

Built from the new pipeline

The new pipeline is the authority for credential qualification. These numbers are read from the qualification view derived from the official credential-eval run of the public-evidence-snapshot population. The regression and policy populations keep their own counts on the qualification pages and are not added in here.

Authority: new
Population: public-evidence-snapshot
Engine: credential-eval 0.1.0-alpha.16
Evidence: snapshot-2026.10.06.4
Run: sha256:4bec6e539482…
Recorded: 2026-10-07
Authorised for: @redact-secret/core@0.1.0-beta.14

Maintainer-reviewed (independent review pending)

598 fixtures of the 7,041 in evidence release snapshot-2026.10.06.4 carry this label. They are counted in the numbers on this page.

Passed the project’s own verification (source evidence, automated checks, recorded counter-arguments); not yet independently reviewed.

OpenRedaction default (all patterns): not measured in this run (optional)

The default (all-pattern) profile is slow and noisy for credential evaluation: personal data and resource identifiers dominate its findings, and its last official measurement took 7 minutes of scanner time on a population the credential profile scans in seconds (its methods run takes 40+ minutes), so it is a manual measurement and never blocks other scanners or core verification (#763). Its earlier results stay as history with their run identity; the credential profile is a separate scanner, never spliced with it.

Last measurement: policy-corpus@linux-x64 (configuration sha256:2451ce7bf380), public-evidence-snapshot+methods@linux-x64 (configuration sha256:d47d081ce5fb), public-evidence-snapshot@linux-x64 (configuration sha256:2451ce7bf380), regression-corpus@linux-x64 (configuration sha256:2451ce7bf380) · engine 0.1.0-alpha.5 · recorded 2026-10-05 · retained record, no longer listed by the run registry. It stays labelled with that run identity and is never combined with another profile or another run.

Open the qualification page for this pointer

OpenRedaction credential profile (33 types): not measured in an official run (local exploratory diagnostics only: see ADR)

The credential profile is the comparison profile chosen in docs/decisions/2026-10-06-choose-the-openredaction-credential-bearing-profile-as-the-comparison-scanner.md. It is optional in the official run class because no pinned engine configuration measures it yet: making it required would refuse every official view until the owner approves the one profile-only run. Its own history starts with that run; nothing of the default's is reused for it.

No earlier measurement of it is recorded. Nothing is shown in its place.

Official measurement: pending: requires owner approval (one profile-only run; see the decision).

Open the qualification page for this pointer

Every population and its qualification

Research record

From credential-evidence snapshot-2026.10.06.4 · records at 77ce761 · schema 1.8.0. It describes the research on the format, not what any scanner or the product does, and not a support status.

Review stateDraft, not reviewed
Format revision1 · current
ResearchResearched
Researched2026-09-24

3 events in the review history: 2 observed, 1 reviewed. Latest: observed on 2026-09-24 by automation, project maintainer. Project-maintained review is not independent validation. The family record at this release.

Format

Provider format research from credential-evidence snapshot-2026.10.06.4 · records at 77ce761 · schema 1.8.0.

What it looks like

Descriptive pattern: ^r8_[A-Za-z0-9_-]{37}$

Parts are shown as recorded. Evidence classes belong to the facts below; no class is assigned to a part.

Format facts

Provider documented · provider-source · current · observed 2026-09-24
Replicate API tokens page ("40-character strings that always start with r8_"): Replicate states that API tokens are 40-character strings that always start with r8_, fixing the prefix and a 37-character body. The page states no body alphabet.
- replicate.com/docs/topics/security/api-tokensprovider-documentation · last read 2026-09-24 · latest outcome read · supports Replicate states that API tokens are 40-character strings that always start with r8_, fixing the prefix and a 37-character body. The page states no body alphabet.
Unresolved · tool-corroboration · current · observed 2026-09-24
Pinned scanner rules are consistent with the contract grammar (1 artifact: trufflehog 3.97.4).
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/replicate/replicate.goscanner-rule-source · last read 2026-09-24 · latest outcome read · supports trufflehog 3.97.4: Replicate: \b(r8_[0-9A-Za-z-_]{37})\b
Provider documented · field-prefix · current · observed 2026-09-24
prefix: r8_
- replicate.com/docs/topics/security/api-tokensprovider-documentation · last read 2026-09-24 · latest outcome read · supports prefix: r8_
Provider documented · field-total-length · current · observed 2026-09-24
total-length: 40 characters (37-character body after r8_)
- replicate.com/docs/topics/security/api-tokensprovider-documentation · last read 2026-09-24 · latest outcome read · supports total-length: 40 characters (37-character body after r8_)
Tool corroborated · field-body-alphabet · current · observed 2026-09-24
body-alphabet: [A-Za-z0-9] in every positive; TruffleHog also admits - and _, flare-redact and agent-sweep admit alphanumerics only (The provider does not state a charset. The contract pattern admits the union so only a non-word byte counts as an alphabet mutation.)
- flare-collection/flare-redact @ c652ea7946028b70527069d7c282752b8a0ccee3: spec/detectors.jsonscanner-rule-source · last read 2026-09-24 · latest outcome read · supports r8_[A-Za-z0-9]{30,45} · #L1352
- trufflesecurity/trufflehog @ v3.97.4: pkg/detectors/replicate/replicate.goscanner-rule-source · last read 2026-09-24 · latest outcome read · supports body class [0-9A-Za-z-_]{37}; its own test fixture is alphanumeric
Provider documented · field-header-scheme · current · observed 2026-09-24
header-scheme: Authorization: Bearer <token>; the legacy Authorization: Token <token> is still accepted
- replicate.com/changelog/2024-04-03-bearer-tokensprovider-documentation · last read 2026-09-24 · latest outcome read · supports header-scheme: Authorization: Bearer <token>; the legacy Authorization: Token <token> is still accepted
- replicate.com/docs/reference/httpprovider-documentation · last read 2026-09-24 · latest outcome read · supports header-scheme: Authorization: Bearer <token>; the legacy Authorization: Token <token> is still accepted
Unresolved · field-sibling-tokens · current · observed 2026-09-24
sibling-tokens: Whether the cog login token (replicate.com/auth/token) or org-owned and default tokens differ in shape from a created API token
- docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/specifics/replicate_user_access_tokenother · last read 2026-09-24 · latest outcome read · supports sibling-tokens: Whether the cog login token (replicate.com/auth/token) or org-owned and default tokens differ in shape from a created API token
- replicate/cog @ main: pkg/cli/login.goother · last read 2026-09-24 · latest outcome read · supports sibling-tokens: Whether the cog login token (replicate.com/auth/token) or org-owned and default tokens differ in shape from a created API token
Unresolved · listed-references · current · observed 2026-09-24
The legacy contract lists 3 references without stating which property each supports.
- replicate/replicate-python @ main: replicate/client.pyother · last read 2026-09-24 · latest outcome read · supports Listed as a reference by the legacy contract
- replicate.com/changelog/2024-04-03-bearer-tokensprovider-documentation · last read 2026-09-24 · latest outcome read · supports Listed as a reference by the legacy contract
- replicate.com/docs/reference/httpprovider-documentation · last read 2026-09-24 · latest outcome read · supports Listed as a reference by the legacy contract
Provider documented · dossier-research · current · observed 2026-09-24
Legacy dossier research (verdict ready, tier T1) cited 3 sources; the dossier does not attribute sources to individual properties.
- redact-secret/redact-secret @ 8b6a5fde52ecb4dfce13f09c7a947062d21483c7: docs/audits/evidence/726/README.mdproject-research-note · last read 2026-09-27 · latest outcome read · supports Final research evidence recorded by the legacy dossier
- replicate.com/changelog/2024-04-03-bearer-tokensprovider-documentation · last read 2026-09-24 · latest outcome read · supports Cited by the legacy dossier research for this family
- replicate.com/docs/topics/security/api-tokensprovider-documentation · last read 2026-09-24 · latest outcome read · supports Cited by the legacy dossier research for this family
Provider documented · taxonomy-sources · current · observed 2026-09-24
The legacy taxonomy lists 2 sources for this family. The taxonomy records no date; the dossier researchedAt is used as the observed-at date.
- replicate.com/changelog/2024-04-03-bearer-tokensprovider-documentation · last read 2026-09-24 · latest outcome read · supports Listed as a source for this family in the legacy taxonomy
- replicate.com/docs/topics/security/api-tokensprovider-documentation · last read 2026-09-24 · latest outcome read · supports Listed as a source for this family in the legacy taxonomy

Open questions

No open question is recorded for this revision.

Benchmark dossier notes

From the provider dossier, as written. The evidence level above says how well the format is backed; a fact the dossier does not record is not shown.

Shape: prefix r8_, 40 characters in total (a 37-character body). The provider states the prefix and the total length. It states no body alphabet. TruffleHog accepts letters, digits, - and _; flare-redact accepts letters and digits only. No checksum or embedded account id is documented.
Basis: T1 for prefix and length (the API-tokens page). Alphabet: scanner rules only, contested. Both Authorization: Bearer and the older Authorization: Token header are accepted (2024-04-03 changelog), and the docs show a masked example (r8_, two visible characters, asterisks).
Issuance: not attempted. Free accounts can create tokens. Replicate scans public GitHub repositories for committed tokens and disables the ones it finds (it joined the GitHub Secret Scanning Partner Program in 2024-04).
Contract in core: detector-families.md (Beta.8 arrival contracts, frozen in the #726 record linked above; the provider-stated length is exact and the alphabet is provisional).

In this benchmark

Fixture rows on the current run. Counts are for redact-secret in published · redact-secret 0.1.0-beta.14 mode.

Fixtures: 32
Left readable: 0
Redacted too much: 0
False alarms: 0

32 fixtures: 12 expect a redaction, 20 must stay quiet. See every row

redact-secret fixture counts by evidence level
Evidence level	Fixtures	Left readable	Too much	False alarms
T1Provider-documented	12	0	0	0
T2Tool-corroborated	13	0	0	0
T3Project policy	7	0	0	0

Every scanner on the same fixtures

In run order. Counts are what each scanner recorded on this family's fixtures, whichever rules it has; a scanner with no rule for the family has nothing to report on it.

Counts per scanner on this family's fixtures
Scanner	Fixtures	Left readable	False alarms
flare-redactRuntime library · 1.6.1 · Published npm package · secrets-only (pii, generic_assignment disabled) · JavaScript engine1 rule targets it	32	0	1
gitleaksRepository scanner · 8.30.1 · Directory scan · default rulesNo rule maps to it	32	6	1
redact-secretProduct measured here · 0.1.0-beta.14 · Published npm package · default detectors1 detector mapped	32	0	0
trufflehogRepository scanner · 3.97.4 · Filesystem scan · verification disabled1 rule targets it	32	0	0

Benchmark dossier questions

Things the sources do not settle. They are listed so nobody reads them as settled.

Open caveat: Body alphabet is not provider-stated (TruffleHog admits - and _, flare-redact does not); one issued token would settle it (checklist in benchmarks#217).

Looks like it, but isn't

Values the dossier records as resembling this credential without being one.

Collisions: r8.im/<owner>/<model> container registry references and 64-hex model version ids are public and share the r8 stem or sit next to tokens. The cog login token from replicate.com/auth/token may be a different credential; the relation is undocumented and not claimed.

Scanner rules for this family

Mapped by hand (reviewed 2026-09-30) from each scanner's pinned rule file, never from what a scanner found on the fixtures.

Peer scanner rules that target this family
Scanner	Rule	What the rule matches
flare-redact · rules 1.6.1	`replicate_token`	r8_ + 30-45 characters
trufflehog · rules 3.97.4	`replicate`	r8_ + 37 characters

No rule maps to this family in gitleaks, openredaction.

Find

Evidence level

Scanners

32 of 32 rows

Fixtures in this family

32 rows, redact-secret's outcome on each. Rows that need a look come first (0), then the rest in corpus order. Choose "Every scanner" to see each scanner's outcome for the same rows.

Fixtures in API token
Fixture	Kind and evidence	redact-secret
`replicate-api-token-bearer-long-body-twin`replicate · wrong-length	Must not flagT2 · Tool-corroborated · twin	Quiet
`replicate-api-token-chat-paste`replicate · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`replicate-api-token-env-short-body-twin`replicate · wrong-length	Must not flagT2 · Tool-corroborated · twin	Quiet
`replicate-api-token-go-sdk`replicate · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`replicate-api-token-legacy-token-header`replicate · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`replicate-api-token-token-shape-bare`replicate · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`replicate-api-token-token-shape-quoted`replicate · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`replicate-api-token-token-shape-unicode-crlf`replicate · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`replicate-api-token-actions-literal`replicate · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`replicate-api-token-actions-secret-reference`replicate · templated-reference	Must not flagT3 · Project policy	Quiet
`replicate-api-token-base64-input-encoded-value`replicate · benign-encoded-value	Must not flagT2 · Tool-corroborated	Quiet
`replicate-api-token-bearer-header`replicate · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`replicate-api-token-docs-prose`replicate · prose-mention	Must not flagT3 · Project policy	Quiet
`replicate-api-token-env`replicate · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`replicate-api-token-env-template-placeholder`replicate · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`replicate-api-token-go-uppercase-prefix-twin`replicate · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`replicate-api-token-identifier-near-miss`replicate · format-near-miss	Must not flagT2 · Tool-corroborated	Quiet
`replicate-api-token-label-prose`replicate · benign-lookalike	Must not flagT3 · Project policy	Quiet
`replicate-api-token-mask`replicate · benign-lookalike	Must not flagT3 · Project policy	Quiet
`replicate-api-token-masked-docs-placeholder`replicate · documentation-placeholder	Must not flagT3 · Project policy	Quiet
`replicate-api-token-mcp-config`replicate · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`replicate-api-token-mcp-hyphen-prefix-twin`replicate · prefix-near-miss	Must not flagT2 · Tool-corroborated · twin	Quiet
`replicate-api-token-model-version-public-id`replicate · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`replicate-api-token-prefix-only`replicate · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`replicate-api-token-printenv`replicate · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`replicate-api-token-printenv-glued-twin`replicate · boundary-violation	Must not flagT2 · Tool-corroborated · twin	Quiet
`replicate-api-token-python-dot-body-twin`replicate · wrong-alphabet	Must not flagT2 · Tool-corroborated · twin	Quiet
`replicate-api-token-python-sdk`replicate · documented-format-literal	Must redactT1 · Provider-documented	Redacted
`replicate-api-token-reference`replicate · benign-lookalike	Must not flagT3 · Project policy	Quiet
`replicate-api-token-registry-image-public-id`replicate · public-identifier	Must not flagT2 · Tool-corroborated	Quiet
`replicate-api-token-short-body`replicate · benign-lookalike	Must not flagT2 · Tool-corroborated	Quiet
`replicate-api-token-truncated-near-miss`replicate · format-near-miss	Must not flagT2 · Tool-corroborated	Quiet

Sources

Researched 2026-09-24.

Documentation and code

replicate.com/docs/topics/security/api-tokens
replicate.com/changelog/2024-04-03-bearer-tokens

Research log

redact-secret/redact-secret-benchmarks#215Research issue
redact-secret/redact-secret-benchmarks#217Research issue
redact-secret/redact-secret#726Research issue
redact-secret/redact-secret#727Research issue
Final evidence, pinned to a commit/redact-secret/redact-secret/blob/8b6a5fde52ecb4dfce13f09c7a947062d21483c7/docs/audits/evidence/726/README.md