Cowrie Research

skip-company-primary-sources-2026-08-09

3 min read

Skip company primary sources — 2026-08-09

Classification takeaway

Skip now clears the bar for a separate companies/ note because the useful control question is not only how do Go Fast, Smart Relay, Eureka, and Connect work? It is which named operator runs the easiest hosted path for routing, relaying, API access, support, and premium feature gating across that stack? The strongest answer in current primary materials is Skip Protocol, Inc., which explicitly provides the website, the hosted Skip:Go interface, and related services, while also controlling API-key issuance workflow, Smart Relay service behavior, official support channels, and the support / SLA shell around Connect. The protocol-versus-company split matters because Skip’s own terms also say the underlying protocol smart contracts are not part of the services and are not controlled by Skip, which makes the hosted operator boundary easier to isolate rather than weaker.

Primary sources reviewed

  1. Official site — https://www.skip.build/

    • Best high-level operator framing for the current product family.
    • Calls Skip one endpoint for cross-chain control flow and presents Connect as a Skip-run validator-native data product.

  2. Skip Go introduction docs — https://docs.skip.build/go

    • Best concise source for the hosted API posture.
    • Says unauthenticated users get very limited access and should request an API key from Skip.

  3. Skip Go docs index (llms.txt) — https://skip-go.mintlify-go.com/go/llms.txt

    • Best evidence for the breadth of the operator-managed docs surface.
    • Shows Skip owns the documentation lanes for routing, tracking, Smart Relay, API keys, legal/privacy, and Eureka/Connect-adjacent workflow.

  4. API keys docs — https://skip-go.mintlify-go.com/go/general/api-keys.md

    • Strongest source for access mediation.
    • Says API keys are managed by Skip, rate limits and privileged features differ based on authentication, and integrators should open a support ticket in Skip’s Discord to obtain access and establish an official communication channel.

  5. Smart Relay docs — https://skip-go.mintlify-go.com/go/general/smart-relay.md

    • Strongest source for the relayer/operator boundary.
    • Says integrators are strongly advised to activate Smart Relay, that route availability and transaction count can worsen without it, and that Skip dynamically quotes the relaying fee and executes supported cross-chain actions through its relaying workflow.

  6. Go Fast docs — https://skip-go.mintlify-go.com/go/advanced-transfer/go-fast.md

    • Best source for the protocol built by Skip framing.
    • Useful because it shows the product layer includes a permissionless solver protocol, which makes the separate company note sharper rather than redundant.

  7. Connect introduction docs — https://docs.skip.build/connect

    • Strongest source for the support-and-SLA shell.
    • Says Connect comes with a 1-day SLA for adding new feeds plus 24/7 on-call support and maintenance by the Skip team.

  8. Skip Terms of Service — https://skip-go.mintlify-go.com/go/legal-and-privacy/terms-of-service.md

    • Strongest source for the company/legal boundary.
    • Says the agreement is between the user and Skip Protocol, Inc., covers the skip.build website and the hosted Skip:Go interface, and explicitly says the protocol is not part of the services and is not controlled or operated by Skip.

  9. Skip Privacy Policy — https://skip-go.mintlify-go.com/go/legal-and-privacy/privacy-policy.md

    • Best source for the data-handling side of the company boundary.
    • Says Skip Protocol collects and processes web/device data, contact data, analytics, cookies, and session replay for the services.

  10. Skip Go Fast solver README — https://raw.githubusercontent.com/skip-mev/skip-go-fast-solver/main/README.md

  • Useful engineering-level evidence that Skip publishes and steers a reference solver stack.
  • Helps keep the distinction explicit between a permissionless protocol path and the company-run hosted routing / support shell.

Why it belongs in the active corpus

  • Useful comparison point for interop stacks where the protocol story and the hosted operator story have started to diverge.
  • Helpful for reasoning about where practical authority sits when a routing brand controls API access, relayer quality, premium features, support channels, and published docs even if some underlying contracts are public or permissionless.
  • Good companion for other hosted default path over nominally open infrastructure cases such as LayerZero Labs, Flashbots, Jito Labs, and Caldera.

Graph View