Cowrie Research

guardarian-primary-sources-2026-04-27

4 min read

Guardarian primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

What the official materials say

1) Consumer exchange posture and company baseline

  • URLs:
  • Key takeaways:
    • The homepage frames Guardarian as an exchange service provider connecting fiat and crypto since 2017, with broad asset coverage and an account-light consumer experience
    • The public-facing product posture is centered on buying, selling, and swapping crypto, but this alone understates the operational breadth visible elsewhere on the site
    • Even the homepage and navigation already hint at a larger product family, including on/off-ramp, business exchange flows, payments, custody, OTC, and RWA surfaces

2) Embedded on-ramp / off-ramp integration for partners

  • URLs:
  • Key takeaways:
    • The integrate-us page explicitly positions Guardarian as a plug-and-play on-ramp and off-ramp integration provider for third-party platforms
    • The page claims 170+ supported countries, 1000+ supported cryptocurrencies, 30+ fiat currencies, and 20+ major payment methods
    • The integration narrative combines a customizable widget, easy-to-navigate docs, and a “powerful API,” which makes Guardarian look more like embedded exchange infrastructure than a simple referral widget
    • The business page separately highlights business crypto-fiat exchange flows, onboarding, deposit handling, and settlement, reinforcing the B2B infrastructure angle

3) API surface and partner workflow

  • URLs:
  • Key takeaways:
    • The API overview page says partners first sign a contract with Guardarian, receive access to a partner account, obtain an API token, and then implement exchange-rate calculation plus the necessary requests for transaction creation and status handling
    • The public API overview explicitly lists health checks, currency list, market info, estimate, and create transaction methods
    • The docs live on a separate first-party domain at docs.guardarian.com, which is a meaningful structural clue that Guardarian maintains a dedicated developer documentation surface
    • Even where the docs root is sparse in simple fetch mode, the combination of docs root plus API overview page is enough to confirm a real integration and partner-account workflow

4) Payments and settlement expansion beyond simple ramping

  • URLs:
  • Key takeaways:
    • Guardarian Payments is presented as a unified crypto-and-fiat payment acceptance product rather than just a buy-crypto widget
    • The page describes invoice issuance, customer payment-method choice, seamless conversion, real-time transaction notifications, and settlement to either a bank account or a crypto wallet
    • It also positions the product for e-commerce, media, entertainment, gaming, and other online platforms, which broadens the categorization from simple ramping toward payments control-plane infrastructure
    • The product stack visible in navigation also includes G-OTC, G-Custody, and G-RWA, suggesting a wider business suite than the public consumer brand alone implies

5) Sitemap and site-structure clues

Whitepaper / technical-doc status

  • No canonical Guardarian whitepaper or litepaper surfaced in this pass.
  • The strongest current source of truth is the official site plus the integration/API pages, the docs root, and the sitemap/robots surfaces.
  • For future refreshes, the sitemap index is likely the fastest way to rediscover newly added product or region pages.

Research notes

  • Best current category for the library: fiat-crypto on/off-ramp infrastructure / embedded exchange API / crypto-fiat payments control plane.
  • Most important categorization clues:
    • explicit on-ramp/off-ramp integration page
    • partner-account and API-token workflow
    • public transaction/estimate/market-info API summary
    • payments product with conversion and settlement behavior
    • large sitemap-driven operational surface
  • Important caveat: much of the public site is SEO-heavy; the clearest infrastructure signals come from the business, integration, API, docs, and sitemap layers rather than the consumer homepage alone.

Graph View