docs(drift): draft from internal source

[pedromcunha]

Drafted from an internal source repo, requested by @matirelay.

This PR was auto-generated by the reusable-docs-draft-pr workflow from a Claude-drafted update in the source repo. It is opened as a draft — please review, edit as needed, and mark ready for review before merging.

Review checklist

• Content matches the behavior shipped in the source PR
• No internal-only details (service names, file paths, unreleased names, security internals) leaked into the draft
• Conforms to CLAUDE.md style rules
• Cross-references and internal links resolve
• Any Needs human input items from the source comment are addressed

---

Generated by reusable-docs-draft-pr.yml in relayprotocol/agents-config.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
unevenlabs	🟢 Ready	View Preview	Sep 9, 2026, 9:19 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[github-actions]

Claude finished @pedromcunha's task in 1m 24s —— View job

---

Code review

• Gather context (diff, changed file, style guide)
• Check whether the removed chain is referenced elsewhere in the docs
• Review against AGENTS.md conventions
• Post findings

Scope: one row removed from the depository address table — anime / chain id 69000 (references/protocol/depository/addresses.mdx:62 in the pre-image).

No blocking issues. The edit is clean and self-consistent:

• Repo-wide grep for anime and 69000 returns no other matches — no dangling links, no other static table to update.
• Ascending-EVM Chain Id ordering is preserved; the removal leaves no gap in the table markup.
• references/api/api_resources/supported-chains.mdx renders chains through the <Chains /> snippet from the live API, so it needs no companion edit.
• The "85+ chains" / "80+ chains" claims in solutions/*.mdx and references/protocol/overview.mdx:67 are approximations and stay accurate.
• references/protocol/** is out of scope for the AGENTS.md v1 profiles (§1.1), and the edit pattern-matches the surrounding page either way. No frontmatter or heading changes to check.
• Nothing internal-only appears in the diff — it is a deletion only.

Things for the author to confirm

1. I could not verify the change against the source of truth. This environment has no outbound network access, so I couldn't run the generator command in the page comment (references/protocol/depository/addresses.mdx:7) against https://api.relay.link/chains. Worth confirming which of these the source PR actually means, because they imply different edits:

• anime is delisted entirely → removing the row is correct.
• anime is still supported but no longer has a protocol.v2.depository → removing the row matches what the generator would emit (jq would print an empty/null field), so still correct, but the chain remains a supported route and a reader may be surprised to not find it here.

2. Consider regenerating the whole table rather than deleting one row. The page is a snapshot produced by the curl … | jq command at line 7. A one-row hand edit keeps anime in sync but leaves any other drift since the last regeneration — newly added chains, or an address that moved between the two depository addresses in use (0x4cd0…bc31 and 0x5991…ecca). Re-running the generator in this PR would make the page match the API in full instead of in one cell. Fix this →

3. Changelog entry — probably not needed, but your call. AGENTS.md §4.2 routes removals that integrators can observe to a changelog source (references/api/changelog.mdx for the API line). A chain losing depository support is integrator-visible, but this page is a regenerated snapshot rather than a documented endpoint contract, so I'd lean no entry. Flagging it only so the omission is deliberate.
· docs-drift/src-4c98bc11a1-baefe2d

[greptile-apps]

Confidence Score: 5/5

Safe to merge: the documented address table now reflects the active Relay chain catalog.

What we checked:

• Compared the parent and current documentation revisions with a live request to the Relay API and confirmed that the current revision omits the Anime chain 69000 row, aligning with the live catalog.
• Verified that after the change, the documentation has no Anime row for chain 69000, aligning with the live service contract.

Summary

• This change removes the Anime depository entry from the contract-address table. A live request to Relay’s chain catalog returned no Anime chain and no depository for EVM chain ID 69000; the updated table now matches the service. The concern that removing this row would hide a currently supported Anime depository was disproved by that live response.

_{Reviews (1) · Last reviewed commit: "docs(drift): draft from internal source"}