CreateAI API Documentation

Welcome to the CreateAI API documentation. This platform provides access to a wide range of AI models across multiple modalities, including text, audio, and vision. Whether you're looking to generate text, analyze images, or process audio, CreateAI has you covered.

Getting Started

CreateAI offers a comprehensive suite of endpoints for various AI/ML tasks:

• Query: Text generation with a variety of models
• Search: Semantic search and RAG capabilities
• Audio: Speech to text transcription
• Vision: Image analysis and understanding
• Speech: Text-to-speech synthesis
• Reranker: Document reranking for better search results
• Realtime: Real-time speech to speech streaming connections
• Embeddings: Generate vector embeddings for text

Quick Example

import requests

url = "https://api-main.aiml.asu.edu/query" # Replace with the appropriate url of your environment (prod, beta, poc)
headers = {
    "Authorization": "Bearer your_project_service_token",
    "Content-Type": "application/json"
}

payload = {
    "query": "What is the capital of France?",
}

response = requests.post(url, json=payload, headers=headers)
print(response.json())

Authentication

All API requests authenticate with a Bearer token. Which token you use depends on what you're building.

Token	Use it for	Identifies
Service token	Server-side and service-to-service calls	The project
Project owner token	Administrative work via the Manage Project endpoint	The project owner
Project web token	Calls made on behalf of a signed-in ASU user	The user

A service token never expires and carries your project's full quota, so it belongs on a server you control. A project web token is issued per user by ASU single sign-on and lasts 24 hours.

Don't ship a service token in a user-facing app

Anything that runs in a browser or on a user's device — including vibe-coded apps — exposes its credentials to whoever is using it. Use ASU Sign-In to get a per-user project web token instead, and keep service tokens server-side.

See Token Details for the full comparison.

Put your app in front of ASU users

You don't need to build a login screen. Register a redirect URL on your project and CreateAI generates a login link that verifies the user's ASURITE and drops them on your page with a token identifying them.

1. An admin registers your redirect URL and enables the feature.
2. CreateAI generates a login link for that URL.
3. You share the link. Users sign in with their ASURITE.
4. They land on your page with a projectWebToken attached.

Read ASU Sign-In & Redirect URLs for redirect URL rules, multi-audience setups, and troubleshooting.

For AI agents and LLMs

This documentation is published in a machine-readable form, so an agent can read it without scraping HTML.

File	Contents
/llms.txt	The full text of every documentation page in one file
/llms-index.txt	A short index linking each page, with a one-line summary

Every page is also available as plain markdown by appending .md to its URL — for example /endpoints/query.md.

Naming

/llms.txt carries the whole corpus here, and /llms-index.txt is the short index. That's the reverse of the usual llmstxt.org convention, so fetch /llms-index.txt first if you only want to find the right page.

Each page in this site shows whether it's part of the corpus with a badge in its top-right corner.

Base URL

Environment	Base URL
Production	https://api-main.aiml.asu.edu
Beta	https://api-main-beta.aiml.asu.edu
POC	https://api-main-poc.aiml.asu.edu

Next Steps

1. Get your API access
2. Review the available models
3. Pick the right token in Token Details
4. Check rate limits
5. Read about error handling
6. Set up ASU Sign-In if real users will use your app
7. Learn about going live
8. Explore the OpenAI-Compatible API for easy integration

Need Help?

If you need assistance or want to request API access, visit the Access Request page. You can also contact us at #createai-community-hub via slack or email us at aiacceleration@asu.edu