Skip to main content
API key scopes control what operations an API key can perform. This page provides a comprehensive reference of all available scopes across Delino public APIs.

Scope Format

Scopes follow the format: service:resource:action
  • service: The Delino service (e.g., real-prompter)
  • resource: The resource type (e.g., project, prompt, chat)
  • action: The operation (e.g., read, create, delete)

Wildcard Scopes

Full Access

*Grants access to all public API services and operations

All Real Prompter Operations

real-prompter:*Full access to Real Prompter service

Real Prompter Scopes

Real Prompter provides prompt engineering through interactive conversations.
real-prompter:project:create
scope
Description: Create new prompt projectsUse Cases:
  • Automated project provisioning
  • Integration tools that create projects
  • Workflow automation
real-prompter:project:read
scope
Description: View project informationUse Cases:
  • Dashboard applications
  • Project listing tools
  • Monitoring systems
real-prompter:project:delete
scope
Description: Delete projectsUse Cases:
  • Admin tools
  • Cleanup automation
  • Project management integrations
real-prompter:prompt:create
scope
Description: Create and improve promptsUse Cases:
  • Prompt creation tools
  • Automated prompt generation
  • Content creation workflows
real-prompter:prompt:read
scope
Description: View prompt content and versionsUse Cases:
  • Prompt browsers
  • Version control integrations
  • Analytics tools
real-prompter:prompt:improve
scope
Description: Request prompt improvementsUse Cases:
  • AI-assisted prompt optimization
  • Automated refinement workflows
  • Quality enhancement tools
real-prompter:prompt:revert
scope
Description: Revert to previous versionsUse Cases:
  • Version management tools
  • Rollback automation
  • Change control systems
real-prompter:chat:send
scope
Description: Send messages in chat sessionsUse Cases:
  • Chat bots
  • Interactive applications
  • Automated conversation tools
real-prompter:chat:read
scope
Description: View chat historyUse Cases:
  • Chat viewers
  • Analytics tools
  • Conversation export tools
real-prompter:chat:delete
scope
Description: Delete chat messagesUse Cases:
  • Moderation tools
  • Privacy management
  • Data cleanup automation
real-prompter:subset:create
scope
Description: Create prompt subsetsUse Cases:
  • Organization tools
  • Categorization automation
  • Workflow management
real-prompter:subset:read
scope
Description: View prompt subsetsUse Cases:
  • Browsing tools
  • Analytics dashboards
  • Export utilities
real-prompter:diagram:read
scope
Description: View project diagramsUse Cases:
  • Visualization tools
  • Documentation generation
  • Project overview displays
real-prompter:*
scope
Description: All Real Prompter operationsGrants access to all Real Prompter service operations including projects, prompts, chats, subsets, and diagrams.

Scope Validation

How Scopes Are Validated

When an API request is made with an API key:
  1. Extract Token: The API key token is extracted from the request
  2. Retrieve Scopes: The key’s scopes are fetched from the database
  3. Check Permission: The required scope is checked against the key’s scopes
  4. Wildcard Matching: Wildcards are evaluated hierarchically
  5. Grant/Deny: Access is granted or denied based on the match

Validation Rules

// Scope: ["*"]
// Matches: Any operation on any service
hasPermission("*", "real-prompter:project:read") // ✅ true
hasPermission("*", "real-prompter:prompt:create") // ✅ true
hasPermission("*", "real-prompter:chat:send") // ✅ true

Common Scope Combinations

Read-Only Access

{
  "scopes": [
    "real-prompter:project:read",
    "real-prompter:prompt:read",
    "real-prompter:chat:read"
  ]
}
Perfect for dashboards and reporting tools that need to display project and prompt information.

Content Creation

{
  "scopes": [
    "real-prompter:project:create",
    "real-prompter:prompt:create",
    "real-prompter:prompt:improve"
  ]
}
For tools that create and optimize prompts but don’t need deletion permissions.

Chat Bot Integration

{
  "scopes": [
    "real-prompter:chat:send",
    "real-prompter:chat:read"
  ]
}
Enable interactive chat features without project management access.

Full Project Management

{
  "scopes": [
    "real-prompter:project:*",
    "real-prompter:prompt:*",
    "real-prompter:subset:*"
  ]
}
Complete control over projects, prompts, and organization without chat access.

Full Platform Access

{
  "scopes": ["*"]
}
Complete access to all Real Prompter operations (use with caution).

Best Practices

Begin with the minimum required scopes and add more only when needed.Example: Start with real-prompter:project:read instead of real-prompter:*
For specific resources, use resource-level wildcards instead of service-level access.Example: Use real-prompter:project:* instead of real-prompter:* if only managing projects
Create different keys for different purposes with appropriate scopes.Example: Separate keys for read-only dashboards, chat bots, and project management
Document why each scope is needed in your internal documentation.Example: “real-prompter:chat:send - Required for customer support chatbot integration”
Review scope assignments regularly and remove unnecessary permissions.Example: Monthly audit of API keys and their scopes

Next Steps