Notus primary sources — 2026-05-02

Project status in this pass

  • No canonical standalone whitepaper or litepaper surfaced.
  • The clearest current source of truth is the Notus docs corpus, especially the API introduction, guides, and llms-full.txt export.
  • The homepage is useful for positioning, but the docs are much clearer about the actual operating surface.

Primary-source snapshots

1) Homepage

  • URL: https://notus.team/
  • Key excerpt:
    • The homepage says teams can quickly launch stablecoin apps with embedded fiat ramps, frictionless wallets, and gasless transactions through one API.
    • It positions Notus for wallets, remittances, and asset-management use cases.
    • It also frames the value proposition around avoiding seed phrases, gas fees, compliance headaches, and long integration cycles.

2) API introduction

  • URL: https://docs.notus.team/docs/api-reference
  • Key excerpt:
    • The introduction says Notus lets teams build Web3 applications with smart wallets, compliance, and seamless fiat integration.
    • It explicitly lists social-login ERC-4337 wallets, gasless DeFi apps, liquidity-pool platforms, compliant exchanges with KYC/AML and fiat on/off-ramps, analytics, and custom UserOperations.
    • This makes clear that Notus is packaging multiple infrastructure layers into one API surface.

3) Quickstart guide

  • URL: https://docs.notus.team/docs/guides/quickstart
  • Key excerpt:
    • The quickstart walks through creating an organization, creating a project, receiving an API key automatically, and configuring fees plus a treasury address.
    • This is a strong clue that Notus is operating a business-facing control plane, not only a raw SDK or library.

4) Gasless transfer guide

  • URL: https://docs.notus.team/docs/guides/gasless-transaction-abstraction/send-transaction
  • Key excerpt:
    • The guide shows how to register a smart wallet address, request a transfer quote, sign it with an EOA, and execute the transfer through the Notus API.
    • It says gas and partner fees can be paid with an ERC-20 token held in the smart wallet rather than requiring native gas tokens.
    • This is a concrete example of Notus packaging account abstraction and gasless UX into its core product.

5) Custom UserOperation guide

  • URL: https://docs.notus.team/docs/guides/custom-user-operation
  • Key excerpt:
    • The docs show that Notus supports composing multiple contract calls into a single UserOperation.
    • The guide includes wallet registration, user-operation creation, and signed execution against the API.
    • This suggests Notus is not only abstracting simple transfers but also higher-level programmable smart-wallet workflows.

6) Analytics overview

  • URL: https://docs.notus.team/docs/guides/analytics-overview
  • Key excerpt:
    • The analytics module is described as a dashboard for user activity, transaction volume, revenue, most traded assets, and liquidity.
    • It also claims compliance/security value by exposing structured onchain data for anomaly detection and operational monitoring.
    • This broadens Notus from transaction execution into measurement and operational intelligence.

7) llms-full.txt docs export

  • URL: https://docs.notus.team/llms-full.txt
  • Key excerpt:
    • The export reproduces the product taxonomy in a machine-readable form, including the API introduction, analytics overview, custom UserOperations, and DeFi/cross-chain guides.
    • It is particularly useful here because it exposes docs breadth even when individual routes are harder to discover from the homepage alone.

Working conclusion

Notus is best cataloged as a stablecoin app infrastructure and account-abstraction control plane: a unified API and dashboard for onboarding users, provisioning smart wallets, enabling gasless and programmable transactions, wiring in fiat/compliance flows, and monitoring operations through analytics. The strongest evidence in this pass was the combination of smart-wallet registration, gasless execution, custom UserOperations, compliant-exchange positioning, and dashboard-level fee/treasury configuration.