Skip to main content
Asteroid integrations are called “workflows”. A workflow consists of a number of steps. Each step can be an AI agent, or code, or both. Each time you execute a workflow, it loads the healthcare portal, carries out your task, and returns data you asked for.

​
Why use Asteroid?

Asteroid manages all of the complexity of integrating with healthcare systems. Features include: Pre-built integrations for hundreds of healthcare systems
Build new integrations in minutes
Managed browser, Linux or Windows computer that your integration needs
Credentials and authentication handled for you
Workflow optimizations to make them cheaper and faster
Notificaitons and alerting if your integration breaks
Fallback back to AI if the website changes
Integrations fixed automatically for you
 Asteroid is designed to be the one-stop-shop infrastructure provider and platform for integrating with any healthcare system.

​
Who uses Asteroid?

Customers today are using Asteroid to do things like:
  • Sign in to a healthcare portal, fill in a long form, read the submission code and return it
  • Open a program on a Windows machine, sign in, export a list of 100,000 patients, and return the data as a file
  • Read a phone call transcript from an AI phone call with a patient, and fill in clinical form
Asteroid is HIPAA compliant, and handles millions of these tasks per year, across hundreds of portals.

​
Speed and cost

Our pricing is visible on https://asteroid.ai/pricing. We charge based on the amount of AI you use, and how long your workflows take to run. Some executions can cost as little as $0.01 or less to run, whilst more expensive agentic, long running tasks might cost $5 or more. Some workflows take as little as a few seconds to run, whilst others can take over an hour. This depends on the complexity of the task and how much AI you use (using AI makes the executions slower). You’re able to easily optimise your workflows using our assistant Astro, giving you full control of your spend.

​
Start here

I want to build a workflow

Create a workflow, run it, and read the result.

I have a workflow and want to call it

Start an execution from your own code and get the data back.

​
A workflow is a graph

A workflow is a graph of small steps. Each step is written in plain English. Each node does one narrow job. A transition decides which node runs next. When you run a workflow, it starts, does some work, and ends. That’s called an “execution”. Small steps keep a workflow predictable. You can see where an execution went wrong, then fix that one node. Read Workflows are graphs.

​
You build it, then you call it

Build a workflow in the platform. To do this, you’re best off using Astro, our assistant. Describe the task to Astro, and it drafts the graph for you. See Build in the platform. You can also build from your coding agent. Your editor reads the graph, changes it, and publishes it. See Build from your coding agent. Both routes produce the same workflow. You then call it from your own systems by API, or via a batch (from a Google Sheet for example). See Call a workflow from your code.

​
Where a workflow runs

Every execution gets an isolated sandbox depending on where the program that you’re integrating with runs. Pick the environment that matches the software you drive. Read Environments.

​
More examples of what people build

Healthcare workflow automation

Claims, prior authorization, revenue cycle, and EHR work on HIPAA-sensitive data.