LogoLogo
  • OVERVIEW
    • What is Dormint?
    • Problem statement
    • Solution
    • User types & Use cases
  • GETTING STARTED
    • How to start?
    • Creating your first AI Agent
    • Using marketplace to buy an Agent
    • Requesting a custom Agent
  • ARCHITECTURE
    • Functional layers
    • Nodes & Node-Based Logic
    • Templates & Gamification
    • Public API Access
    • Analytics & Real-Time Monitoring
  • Marketplace & Contributors
    • Marketplace & Contributors
    • Custom Agents
    • Submitting Nodes & Templates
  • Advanced topics
    • What's AI Sleep Agent?
      • Main features
    • Scaling & Performance
  • ECONOMY
    • Revenue streams
    • Tokenomics
      • $DOAI utility
      • Buyback & Burn Deflationary Mechanism
  • ROADMAP
  • TEAM & ADVISORS
  • GLOSSARY
  • FAQ & Troubleshooting
    • Common questions
    • Tech support
  • Changelog
Powered by GitBook
On this page
Export as PDF
  1. ARCHITECTURE

Public API Access

Public API Access

Many AI Agents need to communicate with external apps or devices. Dormint provides an API layer for each agent:

  1. Agent Endpoint

    • Each AI Agent has a unique URL path (e.g., api.dormint.io/agents/<agent_id>).

    • External applications can POST or GET data here, triggering the agent’s internal logic.

  2. DOAI Token-Based Usage

    • Each API call requires DOAI tokens to be deducted from the caller’s balance, ensuring sustainable operations.

    • Rate Limiting: Dormint automatically throttles or rejects requests exceeding an account’s token balance or plan limit.

  3. Webhook Support

    • Agents can send real-time updates or alerts back to external systems using configurable webhooks.

PreviousTemplates & GamificationNextAnalytics & Real-Time Monitoring

Last updated 4 months ago