Importing Products
Runtype’s /now flow is backed by public JSON import endpoints. You can use them to preview a product architecture from a hosted JSON file or pasted JSON, then create the product once the preview looks correct.
Raw FPO documents accept version: "1.0", "1.1", or "2.0" ("2.0" is the current default, which nests each inline agent’s runtime fields under agent.config; "1.0" and "1.1" remain valid for legacy flat-agent documents). FPO templates require productObject.version to be one of these same values.
Supported Sources
The import APIs support explicit JSON sources only:
- A2A agent cards
- raw Full Product Object (FPO) JSON
- FPO template JSON
The following are intentionally unsupported:
- GitHub repository homepages
- README and markdown URLs
- raw JSON passed through query params
- generic website or repo crawling
GitHub URLs are supported only when they point to a specific JSON file. github.com/.../blob/... URLs and raw GitHub file URLs are normalized automatically before fetch. Gists must use a raw gist file URL that points to one concrete JSON file.
Import Flow
The import flow has three steps:
- Preview the source with
POST /v1/quick-start/imports/preview - Reload the preview later with
GET /v1/quick-start/imports/:token - Create the product with
POST /v1/quick-start/create
Preview endpoints are public. Product creation requires authentication.
Step 1: Preview a Hosted JSON Document
Use a URL source when you want /now or your own app to preview a public JSON file directly.
Step 1b: Preview Pasted JSON
Use a JSON source when you already have the document in memory and do not want to host it first.
Step 2: Reload a Preview Session
Preview responses return an importToken. Use it to restore the same preview after an auth redirect or page refresh.
Preview sessions currently expire after 30 minutes. If the token is missing or expired, the API returns SESSION_NOT_FOUND.
Step 3: Create the Product
Use the import token to create the product after the preview is accepted.
For raw FPO imports:
For FPO template imports, pass the variable values collected from your UI:
Secret template values are used to resolve the final product object, but they are not stored in preview payloads, quick-start provenance metadata, or the create response.
Deploy to Runtype Buttons
For repository buttons, link directly to a hosted JSON document:
The hosted example files used in this guide live at:
docs/templates/quick-start/customer-support-fpo.jsondocs/templates/quick-start/customer-support-fpo-template.jsondocs/templates/quick-start/deploy-to-runtype.md