Skip to content
Apex Flow

Hub Access

The payer's own rules, inside your product.

The payer’s own rules for billing companies, EHRs, software platforms, pharmaceutical access teams and specialty hubs. Explore published requirements, reviewing entities and missing information for a drug through the browser, API or MCP. Reference questions belong here; patient records belong in a separately authorized practice workflow.

14-day trial. Verified work email. No payment card.

Watch the Hub Access overview

How the engine works: one library, every door

See Hub Access in action

One library, every door.

The KAIS overview: practice workflows and medication reference access for pharma, hubs and platforms.

About five minutes. Read how it works, step by step

Try Hub Access

Explore a brand. Or its neighborhood.

Choose one offered brand or one medication neighborhood, then verify your work email to receive a trial key. Ask reference questions in the browser. The same key scopes API and compatible MCP clients; see the connection requirements below.

  • 14 days
  • 250 questions per day
  • 30 requests per minute
  • No payment card

One trial per verified work email. Your selected scope stays fixed for the trial. Use medication and authorization reference questions only; do not enter patient information, clinical notes or medical records. The sandbox does not determine individual coverage, select treatment or submit requests.

Start your sandbox trial

Read before you register

Fasenra: separate the policy from the patient decision.

Question: “What does Aetna's commercial medical policy ask for when reviewing Fasenra?”

Editorial source walkthrough · Not a live API response

Drug and source
Fasenra (benralizumab). Aetna Clinical Policy Bulletin 0925, commercial medical plans. Published last-review date: August 25, 2026. Source checked October 16, 2026.
What the document distinguishes
Initial treatment and continuation have different criteria. Asthma and EGPA have separate pathways. The bulletin points to separate Medicare criteria.
A question it raises
For the severe-asthma pathway, the document asks about prior therapy and uncontrolled disease. An eosinophil count is one part of a conditional pathway, not a standalone authorization decision.
What remains unknown here
The member's exact product, benefit, assigned reviewer, treatment history and clinical evidence. No patient information is supplied or assessed in this example.
The next action
Confirm the applicable plan and reviewing entity, then use the authorized practice workflow to assemble the required chart evidence for clinical review.

This selected summary illustrates how to read a cited reference. It is not the full criteria, a treatment recommendation or a coverage determination. Open the source for its full conditions and latest revision.

A pharmaceutical or hub team can research a requirement without sending a chart. Answering whether an individual meets it requires verified plan information and clinical evidence in an authorized workflow.

Try an offered reference question

What it answers

Six ways to explore the reference library.

Look for the source, edition and unresolved questions in each response. A missing library result means the answer has not been established from the references held; it does not prove the payer has no requirement.

01

Does it need authorization?

For a payer, plan type, state, date and code: whether prior authorization applies, the published rule it rests on, and the line of the payer's own list it came from.

02

Who reviews it?

Published reviewer and benefit-routing information. When responsibility depends on a member's assigned IPA or a private delegation agreement, it still needs verification outside this reference service.

03

What are the criteria?

The payer's documentation criteria for the drug or service, with the Medicare coverage determinations that cite it, ready to match against the chart.

04

What does this denial mean?

Look up supported claim adjustment and remark codes, their descriptions and reference guidance. A code meaning alone does not establish the cause of an individual denial.

05

What does the drug's access look like?

For a drug in your scope, explore the payers represented in the library: its own policies, mentions in broader documents, benefit information, step edits and renewal requirements. A mention is kept distinct from the drug's own policy.

06

Which neighborhood does it belong to?

Explore the medication's reference neighborhood within your licensed scope. A shared neighborhood does not establish that drugs are interchangeable or covered for an individual patient.

Every door, one engine

Call it from your code, or let your AI agent ask it.

The API and MCP expose the reference engine. The practice software adds a separate authorized workflow for chart evidence, clinician review and packet preparation. A public Hub question never includes a patient chart.

API

A keyed, read-only API

Use your trial key in a server-side Bearer header, never in a URL or public source code. Supply reference parameters only and inspect both the response status and unresolved information.

POST /v1/tools/resolve_requirements
Authorization: Bearer YOUR_TRIAL_KEY
Content-Type: application/json

{
  "payer": "Aetna",
  "plan": "commercial",
  "state": "FL",
  "code": "J0517",
  "dos": "2026-10-15"
}

Base URL: https://kais.apexflowrcm.com. This example requires the Fasenra trial's J0517 access. Use the service date for your reference question. Brand access does not automatically include every billing code; check the scope shown when your key is issued.

MCP

A Model Context Protocol server

Connect a client that supports Streamable HTTP and a Bearer authorization header to https://kais.apexflowrcm.com/mcp. Use the same trial key and scope as the browser. Check your client's authentication support first. Clients requiring OAuth discovery, including ChatGPT configurations that require it, need separate compatibility verification; a URL and key alone do not establish that connection.

tools:
  resolve_requirements
  reviewing_vendor
  coverage_criteria
  denial_code
  drug_access_picture
  neighborhood

Quick start & access help

A trial with clear boundaries.

1. Verify and choose

Open the sandbox, verify your work email and select an offered scope. Save the key securely when issued. The browser, API and compatible MCP clients share its scope and limits.

2. Inspect the answer

Check the source, date and unresolved fields. An empty result means the library did not establish the answer. It does not mean no authorization is required.

3. Handle a refusal

Out-of-scope requests stay refused. An authentication failure requires checking your key or expiry. A rate-limit response requires waiting; repeated retries do not expand the allowance. MCP clients must inspect tool errors as well as HTTP status.

Lost or exposed key?

Contact Hub Access support from your registered work email to request revocation or replacement. Do not include the key. Owner verification is required; this page does not offer instant self-service replacement.

What crosses the connection?

Your reference parameters are sent to the hosted service. Account identity, access scope and usage/security metadata support verification, limits and abuse prevention. No patient data is accepted. Read the Hub Access privacy notice.

The trial limits describe access allowances, not a throughput commitment or uptime SLA. Production scope, client compatibility and service terms are established separately.

Who it is for

Built for the teams that move a patient to the first dose.

Pharmaceutical hub and patient-access teams

Compare published requirements for a brand and identify where plan-specific information is still needed. Member benefit verification and patient-level evidence review remain separate from this public reference service.

Specialty pharmacies

Research requirements, reviewing entities and documentation questions before the referral is worked. Resolve missing member and plan information through the authorized workflow.

EHRs, billing platforms and AI builders

Payer intelligence as a service inside your product, on licensing paper. The library stays with us; the cited answers flow to you.

How it is built

Read-only, cited, and private by design.

  • No patient data. Inputs are a payer, a code, a state, a date, a plan type or a denial code. A field that looks like a member ID is refused before the engine is called.
  • Inspect the source. Review the named document and available edition/date information. A held or missing reference is not a positive coverage answer.
  • Visible limits. A missing answer may reflect a library gap, a missing plan detail or a reference that stops short of the answer.
  • Read-only reference tools. They do not submit authorizations or write clinical records. Account, security and usage records support access and quotas.
  • Hosted on AWS. Runs on the hosted KAIS service, keyed per licensee.
  • Defined coverage. Access depends on the offered scope and references held. See the dated library snapshot and counting method.

Licensing

Licensed per brand, per program, or per platform.

Tell us the brand, payer products, intended users and connection method. Start with synthetic reference questions, then agree on licensed scope and a written evaluation scorecard. Real case records require separate authorization and data-handling arrangements.

Hub Access puts the cited rules inside your product or workflow. For a research view of a whole disease across the payers, for your own market access and medical affairs teams, that is KAIS Atlas.

sales@apexflowrcm.com