Environments

Photon has two environments. They run the same API but keep separate data, accounts and credentials.

Neutron

The sandbox, at *.neutron.health. Build and test here.

Photon

Production, at *.photon.health. Real patients and pharmacies.

	Neutron (sandbox)	Photon (production)
Use it for	Building and testing	Real patients and real prescriptions
Prescriptions	Never sent to a real pharmacy	Sent to pharmacies
Patients	Fake ones only	Real
API credentials	Free with every sandbox account	Launch and above
Prescribe app	rx.neutron.health	rx.new (private preview)
Dashboard	app.neutron.health/settings	app.photon.health/settings

Build everything against Neutron. Every link and example in these docs points there unless it says otherwise.

URLs

Every URL follows from the environment’s name, so switching environments means changing one word. The one exception is the Prescribe app, which is rx.new in production. The production Prescribe app and production MCP are in private preview. To get access, ask your Photon contact.

Service	Neutron	Photon
GraphQL	`https://network.neutron.health/graphql`	`https://network.photon.health/graphql` ⚠️
MCP	`https://ai.neutron.health`	`https://ai.photon.health` (private preview)
Prescribe app	`https://rx.neutron.health`	`https://rx.new` (private preview)
Sign-in (Auth0)	`auth.neutron.health`	`auth.photon.health`
Token audience	`https://api.neutron.health`	`https://api.photon.health`

⚠️ Not live yet. network.photon.health/graphql returns a 403 for POST requests. MCP will move to network.<env>.health/mcp, which isn’t live yet.

What’s different in Neutron

Neutron runs the same API, schema, permissions and workflow rules as production, so code that works in Neutron works in Photon. What differs is everything that touches the real world:

	Neutron	Photon
Patient texts	Sent, to the phone number on the patient. Use a number you control.	Sent
Pharmacies	Nothing is transmitted. Orders stay `SUBMITTED` and are never placed or filled.	Sent to the chosen pharmacy, then filled
Webhooks	No `order:placed`, `order:fulfillment` or `order:completed`, because orders never reach a pharmacy	Every event
Prices	Real when a pharmacy returns one, but many options have none	Real
Screening	The same as production
MCP `rx_send`	Creates test orders only	Sends real orders
Patients	Use fake patients only	Real patients
Accounts, teams, catalog, templates	Separate. Nothing carries over.	Separate
Credentials and webhook subscriptions	Separate. Set them up again for production.	Separate

Rehearse everything up to the send in Neutron: sign-in, drafting, screening, signing, sending, the patient’s text, and handling changes and errors. You can’t rehearse fulfillment there yet. Build your webhook handlers from the example events, then confirm them with a small production pilot.

Which host and credential

For each job, call this host with this credential. In production, change neutron to photon, and use rx.new for the Prescribe app.

Job	Host	Credential	Plan
Prescribe	`rx.neutron.health`	The prescriber’s sign-in	Indie
Open the app on a patient or order (deep link)	`rx.neutron.health/order/…`	The prescriber’s sign-in	Indie
Draft in Claude or ChatGPT (MCP)	`ai.neutron.health`	The prescriber’s sign-in, over OAuth	Indie
Manage credentials, team, catalog and templates (dashboard)	`app.neutron.health/settings`	An Administrator’s or Developer’s sign-in	Indie
Embed with the iframe	`rx.neutron.health/order/embed`	The prescriber’s sign-in, with your Application `client_id` in a URL built by `frame()`	Launch
Embed with React or the JavaScript client	`environment="neutron"`	Application `client_id`	Launch
Get a machine token	`auth.neutron.health/oauth/token`	Backend `client_id` and `client_secret`	Launch
Sync patients, draft prescriptions and orders (GraphQL)	`network.neutron.health/graphql`	Machine token	Launch
Send a signed order from your backend	`network.neutron.health/graphql`	Machine token. A prescriber must have signed every prescription.	Launch
Draft from another MCP client, such as a scribe, for a prescriber	`ai.neutron.health`	The prescriber’s sign-in, from a client allowlisted on your Application credential	Launch
Draft from your own agent (MCP)	`ai.neutron.health`	Machine token. It can’t sign.	Launch
Receive order updates (webhooks)	Your own HTTPS endpoint	The shared secret you set	Launch

The plan is the smallest one that includes the job. In the sandbox, every account can do all of them. See Use cases.

In code

Prescribe and the JavaScript client take the environment’s name:

<PhotonProvider clientId="YOUR_CLIENT_ID" environment="neutron">

const ph = photon({ environment: "neutron", auth: { clientId: "YOUR_CLIENT_ID" } });

PhotonProvider defaults to production (photon). Set environment="neutron" while you build.

For GraphQL or MCP, use the URLs above.

Going live

Choose a plan. API credentials need Launch or above. Start a production account, or email sales@photon.health to talk through your use case. The production Prescribe app and MCP are in private preview, so ask your Photon contact for access.
Get production credentials from app.photon.health. Sandbox credentials don’t work in production.
Invite your prescribers to the production organization, with their NPI, phone, fax and address. Nothing carries over from Neutron. See Team.
Change the environment from neutron to photon: the environment prop, or the hostnames for GraphQL and MCP.
Add your production domain to your Application credential’s allowed URLs. Using the iframe? Add https://rx.new too.
Set up your webhooks in production too.

Get started

Integrations

Fundamentals

Admin

Resources

URLs

What’s different in Neutron

Which host and credential

In code

Going live

​URLs

​What’s different in Neutron

​Which host and credential

​In code

​Going live

URLs

What’s different in Neutron

Which host and credential

In code

Going live