> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mirurobotics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

export const CardNewTab = ({children, ...props}) => {
  const ref = React.useRef(null);
  React.useEffect(() => {
    if (!ref.current) return;
    const anchor = ref.current.querySelector('a[href]');
    if (anchor) {
      anchor.setAttribute('target', '_blank');
      anchor.setAttribute('rel', 'noopener noreferrer');
    }
  }, []);
  return <div ref={ref} style={{
    display: 'contents'
  }}>
      <Card {...props}>
        {children}
      </Card>
    </div>;
};

The Miru Device API is a REST API with Server-Sent Events (SSE) streaming for programmatically interacting with the Miru Agent from an application running on the same device as the agent.

The Device API is not available over the internet—it is only accessible from the device running the Miru Agent. It is useful for manually refreshing configurations, retrieving current configurations, checking agent status, and receiving [real-time events](/developers/device-api/events) from applications running on your devices.

The Device API is distinct from the Miru [Platform API](/developers/platform-api/overview), which is a REST API for backend services and CI/CD pipelines to manage Miru resources.

To get started, continue to the [Authentication](/developers/device-api/authn) page to learn how requests are authenticated. For a complete reference of all available API endpoints, visit the Device API Reference.

<CardNewTab title="Device API Reference" icon="bot" href="/references/device-api" arrow>
  Complete reference of all API endpoints exposed by the Miru Agent.
</CardNewTab>