Documentation Index

Fetch the complete documentation index at: https://koreai.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

​

Community & Support

Find help, connect with other developers, report issues, track releases, and monitor the operational status of the Platform.

---

​

Get Help

​

Documentation

This docset contains tutorials, how-to guides, the ABL language reference, and the REST API reference. Relevant ones are:

1. Platform overview to know the Platform.
2. Quickstart to build a foundation.
3. Glossary to get familiar with terms.

​

Community Forum

Join the Agent Platform community forum to ask questions, share patterns, and learn from other developers building with the platform. The platform team and experienced community members monitor the forum.

• General discussion: Architecture questions, best practices, and design patterns.
• Troubleshooting: Help with errors, unexpected behavior, and configuration issues.
• Show and tell: Share what you have built and get feedback from the community.

​

Slack Community

Request an invite to the Agent Platform Slack workspace for real-time discussions with other developers and the platform team. Slack is best for quick questions, live debugging sessions, and casual conversation.

​

Stack Overflow

Tag your questions with abl-platform on Stack Overflow for community-driven answers. The platform team monitors this tag and contributes answers.

​

In-App Support

Click the Help button (question mark icon) in the bottom-right corner of Studio to open a support chat. For email support, contact Support. Enterprise customers have access to a dedicated Slack channel and account manager for priority assistance.

---

​

Contributing

The Agent Platform documentation is maintained alongside the platform source code. To contribute:

1. Report documentation issues by creating an issue with the docs label. Include the page URL and a description of what is incorrect, unclear, or missing.
2. Suggest edits by submitting a pull request with your proposed changes. Follow these guidelines:
   • Write in second person (“you”), active voice, present tense
   • Use sentence case for headings
   • Avoid words like “simply,” “just,” “easily,” or “obviously”
   • Include code examples where they clarify usage
   • Cross-reference related pages using relative paths
3. Review the ABL language reference before submitting documentation changes.

---

​

Partner Program

The Agent Platform partner program is designed for system integrators, consultancies, and technology companies building solutions on the platform.

​

Partner Benefits

• Early access: Preview upcoming features and API changes before general availability
• Technical support: Direct access to the platform engineering team for architecture guidance
• Co-marketing: Joint case studies, blog posts, and event participation
• Training: Dedicated onboarding sessions and advanced workshops
• Partner directory: Listing in the platform’s partner directory for customer referrals

​

Becoming a Partner

To learn more about the partner program or apply, contact partners@ablplatform.com with:

• Your company name and website
• A brief description of your use case or solution
• Your expected deployment scale (number of agents, sessions, tenants)

---

​

Support Tiers

Your support tier is determined by your plan tier. Contact your account team to discuss support options.

---

​

Changelog

Stay informed about new features, improvements, bug fixes, and breaking changes in the Agent Platform.

​

How to Follow Updates

• RSS feed: Subscribe to platform updates via the RSS feed for automatic notifications.
• In-app notifications: The Studio dashboard displays a banner when a new release is available.
• Email digest: Enable release notifications in your account settings under Preferences > Notifications.

​

Versioning Policy

The Agent Platform follows semantic versioning for its API and SDK releases:

• Major versions (e.g., 2.0.0) introduce breaking changes that require migration steps.
• Minor versions (e.g., 1.3.0) add new features in a backward-compatible manner.
• Patch versions (e.g., 1.3.2) contain backward-compatible bug fixes and security updates.

Platform services (Runtime, Studio, SearchAI) are versioned together. SDK packages maintain their own version numbers but are tested against the corresponding platform release.

​

Breaking Changes Policy

When a release contains breaking changes, we:

1. Announce the deprecation at least one minor version in advance.
2. Provide a migration guide with step-by-step instructions.
3. Maintain backward compatibility for deprecated features during a transition period (typically 90 days).
4. Mark breaking changes with a BREAKING label in the release notes.

​

Release History

​

v1.0.0 (upcoming)

Initial general availability release. New:

• Agent Blueprint Language (ABL) parser, compiler, and runtime
• Studio visual editor for agents
• Multi-agent orchestration with supervisor, delegation, and handoff
• Knowledge base management with RAG pipeline (SearchAI)
• GATHER construct for structured data collection with LLM inference
• Guardrail pipeline with rule-based, model-based, and LLM-based safety checks
• Observatory for real-time session monitoring and trace inspection
• Role-based access control with tenant and project scoping
• SDK channels for web, React, and REST API integration
• Webhook delivery with idempotency and automatic retry
• SSO support via SAML 2.0 and OpenID Connect
• Multi-tenant resource isolation with per-tenant LLM policies

Improved:

• ABL compiler output optimized for reduced IR payload size
• Session state compression for lower storage costs
• Knowledge base ingestion pipeline with parallel chunk processing

​

Upcoming Releases

Planned features and improvements are tracked on the public roadmap. To request a feature or vote on priorities, visit the roadmap page or contact your account team.

---

​

Platform Status

Monitor the operational status of all Agent Platform services in real time.

​

Status Page

For live status information, visit status.ablplatform.com. The status page provides:

• Real-time status of all platform services
• Uptime metrics for the current month and historical periods
• Active incident details with ongoing updates from the engineering team
• Scheduled maintenance windows with advance notice

​

Monitored Services

​

Subscribe to Status Updates

Stay informed about incidents and maintenance without manually checking the status page:

• Email notifications: Subscribe on the status page to receive alerts for incidents, maintenance, and resolution updates.
• RSS feed: Add the status RSS feed to your feed reader.
• Webhook integration: Configure a webhook on the status page to receive status change events in your own monitoring systems (Slack, PagerDuty, Datadog, etc.).

​

Uptime Commitment

Uptime is calculated as the percentage of time that core services (Runtime and API Gateway) are operational during a calendar month, excluding scheduled maintenance windows announced at least 48 hours in advance. For details on service level agreements (SLAs) and credit policies, refer to your contract or contact your account team.

​

Scheduled Maintenance

Routine maintenance is performed during low-traffic windows and announced at least 48 hours in advance on the status page. Maintenance windows are communicated via status page banner, email notification to subscribed administrators, and in-app banner in Studio. Emergency maintenance for critical security patches may occur with shorter notice. The platform team communicates emergency maintenance through all available channels as the event unfolds.

​

Incident Response

When a service disruption occurs, the platform team follows a structured incident response process:

1. Detection: Automated monitoring detects the issue and alerts the on-call engineering team.
2. Acknowledgment: The incident is acknowledged on the status page within 15 minutes of detection.
3. Investigation: The team investigates the root cause and posts updates at regular intervals (every 30 minutes for critical incidents).
4. Resolution: The service is restored and the status page is updated to reflect the resolution.
5. Post-incident review: A post-mortem summary is published within 5 business days, including root cause analysis and preventive measures.

---

​

Code of Conduct

All community spaces (forum, Slack, GitHub) are governed by our code of conduct. We are committed to providing a welcoming and inclusive environment for everyone. Please treat all participants with respect and professionalism.