Core Concepts
This guide introduces the key concepts used across the AISquare platform.
Understanding these will help you work with the API more effectively and make sense of how different endpoints relate to each other.
AI Studio
An AI Studio is a container for AI content and experiences.
Think of it as a workspace or hub where:
- Content is created and organized
- Users interact with AI experiences
- Engagement and activity are tracked
Each AI Studio is identified by a unique url (publication_custom_url).
Example:
Publication
A Publication represents the underlying entity behind an AI Studio.
It contains:
- Metadata (name, logo, description)
- Visibility settings (public, private, team)
- Associated users (creator and co-creators)
In most APIs, “publication” and “AI Studio” are used interchangeably.
Experience
An Experience is a structured unit of content inside an AI Studio.
It represents a topic, workflow, or learning module.
Examples:
- “Advanced Machine Learning Models”
- “AI in Healthcare”
Each experience contains one or more resources.
Resource
A Resource is the actual content within an experience.
AISquare supports multiple resource types:
Experience vs Resource
This is important:
- Experience = container
- Resource = individual item inside it
One experience can have multiple resources.
Flattened resources
Some APIs return data in a flattened format.
This means:
- Each resource is returned as a separate item
- Experience data is repeated for each resource
Why? It makes it easier for frontend applications to render lists.
Creator and co-creators
See Working with creators for API details.
Each AI Studio has:
Creator
- The owner of the studio
- Manages content and settings
Co-creators
- Collaborators with specific roles
- Can edit, review, or contribute
Each co-creator has:
- Role (editor, reviewer, etc.)
- Status (invited, accepted)
Metrics and engagement
See Metrics and analytics for API details.
AISquare tracks user engagement across experiences and resources.
Common metrics include:
- Views
- Likes
- Shares
- Bookmarks
- Comments
These metrics are used for:
- Ranking (trending, popular)
- Analytics dashboards
- Personalization
Tags and categories
Content can be organized using:
- Tags — flexible labels (e.g.,
machine-learning,ai) - Categories — structured classification
These are used for:
- Filtering
- Search
- Discovery
Collections
See Collections for API details.
A Collection is a curated group of experiences.
You can use collections to:
- Create learning paths
- Group related content
- Organize resources for users
Collections support:
- Ordering of experiences
- Visibility control (public, private, team, org)
Activity
See Activity and personalization for API details.
AISquare tracks user activity across the platform.
This includes:
- Interactions with experiences
- Content engagement
- Progress and history
Activity data powers:
- Personalization
- Recommendations
- Analytics
Permissions and access
See Permissions and access control for details.
Access to content depends on:
- Publication visibility
- User role (creator, co-creator, member)
- Authentication status
Some endpoints require:
- Membership in a workspace
- Ownership or collaborator access
Putting it all together
Here’s how everything connects:
Next steps
Now that you understand the core concepts:
- Follow the Quickstart to make your first request
- Set up Authentication for your integration
- Build your first integration
- Explore AI Studios APIs to fetch content
- Use Collections APIs to organize experiences
- Learn about Content modeling for building your UI
- Understand Search, filtering, and pagination

