docs(drift): draft from internal source

[pedromcunha]

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

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.

[github-actions]

Claude encountered an error after 2m 3s —— View job

---

Reviewing PR #433

• Fetch the PR diff
• Read the changed pages in context
• Check against AGENTS.md style rules
• Post review

[mintlify]

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

Project	Status	Preview	Updated (UTC)
unevenlabs	🔴 Failed	–	Aug 27, 2026, 9:10 PM

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

[greptile-apps]

Greptile Summary

This change removes the notice that Story is unsupported for onramp deep links and removes Story’s depository-address entry. Live Relay API checks show that Story (chain ID 1514) is still absent from the public chains response, so the onramp documentation now suggests availability that integrators cannot discover or use. Restore the unsupported-chain entry until Story is published as an enabled chain.

Confidence Score: 4/5

Not safe to merge as written because the public onramp documentation contradicts the current chain-discovery response.

The Story/1514 path was checked against the live public chains and currencies endpoints and compared before and after the documentation change. The chains endpoint omitted Story in both cases, while only the updated documentation removes its unsupported status.

Files Needing Attention: references/api/api_guides/deep-linking.mdx needs the Story unsupported-chain entry restored. The depository-address removal in references/protocol/depository/addresses.mdx agrees with the chains response.

T-Rex Logs

What T-Rex did

• T-Rex produced a proof for a posted P1 finding.
• The P1 finding proof included artifacts such as the HTTP check source and the contract logs showing before and after the PR, plus a script capture.
• A general contract validation was run to compare the before and after contract states and showed that the chain endpoint still omits Story 1514 and that documentation no longer marks it as unsupported, with the validation exit code 1.
• The validation also confirms that depository-address removal aligns with the chain omission and that onramp-list removal is reflected in the documentation.

_{Ran code and verified through T-Rex}

Comments Outside Diff (2)

1. references/api/api_guides/deep-linking.mdx, line 132-140 (link)

   Story onramp discovery is unavailable

   Removing Story from the unsupported onramp list implies that relay.link/onramp/story is usable, but the public GET https://api.relay.link/chains response still has no Story/1514 chain record. Clients therefore cannot discover Story as an enabled destination, and users following this page cannot complete the documented onramp flow. Restore - Story to this list until the chains API publishes Story as enabled, or enable and publish the chain before removing the exclusion.

   Artifacts

   
   

   Story documentation contract HTTP check source

   • Executable Node script that requests the public Relay chain and currency APIs, reads each documentation revision, and asserts the Story 1514 contract.

   Story documentation contract before PR

   • Executed base-revision check: `/chains` omits Story 1514 and the base documentation still marks Story unsupported, so the documentation contract passes.

   Story documentation contract after PR

   • Executed HEAD check: `/chains` still omits Story 1514 while the changed documentation no longer marks it unsupported, so the documentation contract fails.

   Story documentation contract script capture

   • Captured source of the executed checker, including both exact public request URLs, request body, observations, and assertions.

   

   _{Ran code and verified through T-Rex}

2. General comment

   Story is advertised as an onramp destination although the public chains API omits it

   • Bug
     • references/api/api_guides/deep-linking.mdx removes Story from the explicit unsupported-chain list. However, the live GET https://api.relay.link/chains response contains no chain whose ID, name, or protocol v2 chain ID is Story/1514, so public clients cannot discover Story as an enabled onramp destination. POST /currencies/v2 does return WETH and USDC metadata for 1514, but this does not override the absent chain record required to identify and enable the destination.
   • Cause
     • The unsupported-list entry was removed based on currency metadata or stale deployment information without confirming public chain discovery/onramp availability.
   • Fix
     • Restore - Story to the unsupported-chain list until GET /chains exposes Story (protocol chain ID 1514) as an enabled, non-disabled chain; alternatively publish the chain endpoint support first and then remove the exclusion.

   _{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "Update app.md" | Re-trigger Greptile}