AI, hosting and service catalogues

AI provider and model registry

AI Products is a God-only registry for provider authorisations, registered models and training plans. Authorisation records include developer, inference operator, SDK, relationship designation, evidence reference, status, expiry and separate permissions for inference, reference training, educational data and branding. Model records include display name, upstream model identifier, availability status, inference and training eligibility, and a JSON training policy. These fields determine what the product catalogue may claim; do not mark a provider verified or owner-confirmed without the approved evidence.

1. Open AI Products and expand the provider authorisation or model record to be maintained.
2. Check evidence, expiry, permission flags, upstream identifier and training policy against the approved source.
3. Save and confirm the status and eligibility flags on the registry; correct invalid JSON or stale evidence before publication.

AI hosting model catalogue

AI Hosting administration covers providers, model families, tracks, releases, checkpoints, quantisations and runtimes. Add records in dependency order so each model release points to an existing provider and family. Discovery entries can be reviewed through the catalogue workflow. A catalogue entry describes a supported offering; it does not by itself prove an inference endpoint or deployment is live. Check the relevant release state, provenance and public page after changes.

1. Create or inspect the provider and family before adding a track, release or checkpoint.
2. Enter the canonical model identifiers, runtime and quantisation details from approved source material.
3. Review the resulting model page and registry record; resolve discovery items deliberately rather than accepting them in bulk.

GPU and hosting inventory

The hosting platform screen manages hardware records and inventory, market references and manual price overrides with approval. Import Preview lets an operator inspect a proposed catalogue import before applying an update. Hardware registry entries identify vendors and GPU specifications; inventory indicates offered or tracked capacity and should not be confused with an unverified public claim. Service products have separate price, state and definition controls. Worker pools have their own create and state actions. Keep provider credentials and private deployment values out of descriptive fields.

1. Open AI Hosting and inspect the hardware, inventory and price state before importing or editing.
2. Preview an import, verify vendor/model identity and evidence, and submit only the intended changes.
3. For price overrides or service-product changes, use the approved currency and approval flow, then confirm the resulting state.

Customisation and managed projects

AI hosting customisation presents service products and model-specific options to configure a quote. The public workflow gathers requested requirements and submits a quote rather than silently provisioning infrastructure. Managed Projects lets authorised staff inspect a job, update its status and assignment, upload deliverables, add model versions and change orders, and complete defined stages. Custom quote approval is a separate action. Keep customer work attached to its project record and do not expose its data in public content.

1. Open the service or model configuration and check supported options and required input fields.
2. For an internal project, inspect the quote and job state before changing assignment, stage or deliverables.
3. Submit a change order or quote approval only with the required review; confirm the project timeline reflects the result.

Blockchain service catalogue

Blockchain Commerce administration manages product categories, products, price records, relationships and media. Product and price changes are separate operations; the resulting catalogue can feed customer quote and order flows. The operational order screen is different: support and admin staff handle assigned tasks and record external or governance status, while God maintains the catalogue. Do not describe a catalogue change as a transaction executed on a chain. Verify published product details and any related service order separately.

1. Open Blockchain Commerce and select the product or category; check existing relations and price records.
2. Create or update the catalogue item with its approved description, pricing and media, then save.
3. Re-open the customer-facing catalogue entry and verify the correct category, price and related items.

Banking services and catalogue

God-only Banking Administration lists banking requests and service products. The request detail supports lifecycle transitions and quote preparation; product controls update product state and add price entries. A customer saves a request and submits it through a distinct workflow. Admin acceptance and pricing are not equivalent to initiating a real bank transfer. Check the request and product statuses, supported currency and quote evidence before transitioning. The current admin workflow validates its quoted currency rather than accepting arbitrary values.

1. Open Banking Administration and inspect the service product or request detail and its event history.
2. Update the product or prepare a quote with the supported currency and complete required amounts and terms.
3. Submit the authorised transition, then verify the request status and generated quote in the detail view.

Frequently asked questions

Related pages

• Administration and access control
• Encrypted backups and recovery
• Commercial and finance administration
• Content, localisation and search presentation
• People, teams and recruitment
• Service operations and monitoring
• Support desk and knowledge operations