Skip to content

docs: update sdk docs 2026-08-03 - #103

Open
JamesLawton wants to merge 1 commit into
mainfrom
docs/update-sdk-2026-08-03
Open

docs: update sdk docs 2026-08-03#103
JamesLawton wants to merge 1 commit into
mainfrom
docs/update-sdk-2026-08-03

Conversation

@JamesLawton

Copy link
Copy Markdown
Collaborator

What changed

  • sdk/quote-providers.mdx — add EVERLONG to the "Available Providers" list and add a dedicated section under "Provider Details" describing it (same-chain swap on Katana, exact-input only, explicit selection only — not picked by AUTO).

Source of truth

  • 0xsequence/trails-api#1023 — "Everlong hotfix" cherry-picking #1015 into release, merged 2026-07-28.
  • lib/routes/everlong/everlong.go on release:
    • IsChainSupported: chainID == ChainIDKatana — Katana (747474) only.
    • checkCapabilitiesForRoute: rejects cross-chain (originChainID != destinationChainID returns error) — same-chain only.
    • operations map: RouteOperation_Swap: true, RouteOperation_SwapExactInput: true, RouteOperation_SwapExactOutput: false.
  • lib/routes/routes.go on release: ExplicitOnlySwapRoutes: []string{"EVERLONG"} — the routing solver's ExplicitOnlySwapProvider architecture excludes EVERLONG from AUTO candidate lists (see TestBuildRouteCandidates_ExplicitOnlySwapRouteIgnoredInAuto in lib/intentmachine/routingsolver/route_preference_test.go).

Verification

  • Grep confirms EVERLONG did not already appear anywhere under trails-docs/ before this change.
  • The added prose matches the pattern of the existing OIF / LZ_TRANSFER entries (explicit-only providers).

Generated by the Trails Docs weekly agent.


Generated by Claude Code

Document EVERLONG as a new same-chain swap provider on Katana
(introduced in 0xsequence/trails-api#1023).

Generated by the Trails Docs weekly agent.
@mintlify

mintlify Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated (UTC)
trails 🟢 Ready View Preview Aug 3, 2026, 9:27 AM

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

JamesLawton pushed a commit that referenced this pull request Aug 3, 2026
The previous preview build failed with a generic "unknown error occurred"
from Mintlify (deployment reached "Updating all paths..." after
successfully validating the config and OpenAPI files). The sibling PR
#103 opened seconds later against the same base built cleanly, so this
is a transient Mintlify-side hiccup rather than a diff-side issue —
retrigger by pushing an empty commit.
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.

1 participant