Skip to main content
Use Monid directly when your users never see Monid — it’s an internal building block powering features inside your product. You hold a single Monid account and call the API server-to-server.

​
Use Direct Integration When

  • Monid is a hidden implementation detail (data enrichment, background jobs, agentic tools).
  • You want the simplest possible integration — one API key, no OAuth flow.
  • You bill users through your own system (subscription, per-feature, or free).
  • You want a unified billing surface: one Monid invoice for all usage across your users.

​
Two Patterns

Full discover / inspect / run

Let your backend (or an internal agent) pick endpoints dynamically at runtime. Best when the set of tools needed isn’t known ahead of time.

Curated endpoints only

Pre-select a handful of endpoints and call run on them directly. Best when you want a simple, fixed interface with predictable pricing.

​
Skip Direct Integration When

  • Your users should have their own Monid account and wallet → use OAuth.
  • You want to expose Monid tools to user-owned agents but with your own billing and allowlist → use a Proxy.

​
Examples

Whenever a new contact is created, the CRM’s backend calls a curated Monid endpoint to pull LinkedIn + company data. Users never see “Monid” — they just see enriched contacts. The CRM pays Monid once a month and bills users on its own plan.
A support tool has a “Research this ticket” button. Its internal agent uses Monid discover / inspect / run to find the right data source for each ticket. The user only sees the final summary.
A nightly job runs a fixed set of Monid scraping endpoints to refresh a dataset. No user interaction, no dynamic discovery — just direct run calls on known endpoints.
Ready to build? Continue to Set Up Direct Access.