ModelviaManaged AIDocumentation

DEVELOPER DOCUMENTATION

Connect your business, then serve each customer.

Verify your account and key, give each customer a bounded project, and show their usage in the right console. Payment setup comes after the seller, payer and invoice are confirmed.

Set up your business connection
Already have a project key?Make your first bounded API call

Before you start

Modelvia first confirms your business billing identity, payer and invoice issuer, approved models and limits, and a dedicated client integration key. Keep collection disabled until your seller and method are ready. Documentation and sign-in alone do not create an account, accept terms or enable payments.

Already invited? Sign in to your workspace. Your backend should then make the read-only connection check and compare the returned client ID with the one in your onboarding record. A project key can list its available models, but cannot prove your business-to-customer binding.

Check the models available to an active project
curl https://api.modelvia.dev/v1/models \
  -H "Authorization: Bearer $MODELVIA_KEY"

Run this only after your project is active. It lists permitted models without running a completion. Keep keys on your server. The first-call guide explains the request that can incur usage charges.

Build in this order

  1. Verify the business connection

    Confirm billing ownership and limits, install the server-only client key, then check its exact client ID without sending a billable request.

  2. Bind one customer and project

    Save your customer’s local ID beside the returned Modelvia customer and project IDs. Agree terms, narrow caps and issue one protected project key.

  3. Make one bounded request

    List permitted models, send the request and inspect its receipt. Retry safety with your own idempotency key is optional (advanced). A lost response is not a reason to send a new chargeable request.

  4. Show scoped usage

    Resolve the signed-in person’s stored customer binding on your server and show only their requests, tokens and agreed charges.

  5. Offer payment when ready

    Confirm the issued invoice’s seller and payer, then enable the eligible Square or direct-payment path for that business.

Choose where your customers manage usage

Your customer experience can live in the Modelvia workspace or in your own product. The account and payment permissions still apply in either place.

Use the hosted workspace

Use Modelvia’s existing usage and billing screens for customers whose access has been configured. Workspace sign-in needs a provisioned membership; a project key does not create one.

Understand hosted access

Build into your product

Keep your own sign-in and interface. Your backend uses a client integration key and an authoritative customer mapping to request only that customer’s data.

Follow the console guide

Find the detail you need

  • Product setupCredentials, account hierarchy, backend integration and retries.
  • Receipts and invoicesWhat your customers see of each charge, who used every amount, and how to reconcile an invoice.
  • API referenceAvailable endpoints, authentication and links to request examples.
  • MCP and agent hostsConnect supported agent hosts with the right credential scope.
  • API versioningCompatibility rules and the status of the deprecation policy.