AI Services Agents
Developer console

Agents

Lists agents in the registry with status, runtime, model, and governance profile. Search or filter, then open an agent to manage it.

Name Agent ID Status Runtime Model Updated

Create Agent

Creates an agent. Governance is optional. Optionally map it to a project.

Cancel

Agent Details

Shows this agent’s configuration, governance profile, lifecycle actions, and feedback history.

Agent ID —

Edit Agent

Edits this agent’s name, runtime, tools, data sources, and governance profile. Use Agent Details for activate, disable, or archive.

Agent ID —
Cancel

Query Tester

Runs a live execute call on an active agent. Shows the response, token usage, governance decision, and a form to submit feedback.

Governance

Create and review governance profiles that agents use at execute time. Each profile holds who can call (roles), rate limits, exact pattern redaction/blocks, and custom policy checks evaluated for meaning (not only exact words). Attach a profile on Create or Edit Agent.

Defines a reusable rule pack for a product or project (for example Twym Ops vs Twym Edge). After create, select it on an agent.

Profile catalog

Profiles already available to attach to agents, including which agents use each one and their custom policy checks.

Decision View

Compact audit log of governance checks. Each execute creates two checks by design — before the model (can this caller run?) and after (is the response allowed). Click a row for details.

Projects

Projects are parent containers for agents. After create you can Publish (give others your endpoint + fab_… key) and Connect (attach another Fabric project or external API/MCP with their credentials).

Creates the project in draft lifecycle and issues a default API key. Promote with Test → Activate → Publish on the project page before others can call it.

Project registry

Project

Create → Test → Activate → Publish → Deprecate. Test runs a smoke execute; Activate enables execute; Publish marks the project published.

—

Project profile merges with Global → Team → Agent (deny / stricter wins).

Teams under this project. Each team can have its own governance profile.

Issue endpoints + fab_… keys so other projects/apps can call agents mapped here. Send Authorization: Bearer fab_…. Atlas stays behind Fabric.

Publish modes
—
Example curl (API publish) 

              

            


            

              
              

                Inbound: store their credentials so this project can reach another Fabric project or an external API/MCP.
              

              

                
                
                

                  
                

                
                
                
                
              

              

            


            

              
              

                Attach an existing Fabric agent to this project. Governance stays on the agent (optional).
              

              
              
              
            


            

              
Mapped agents

            

            


            

              
              
              
              
            

            
            
          

        

      


      

        

          

            

              
Knowledge · TwymAtlas

              

                TwymAtlas is Fabric’s only knowledge plane (MCP). Fabric does not host generic or
                local knowledge sources — agents retrieve indexed enterprise knowledge from Atlas
                at execute time.
              

            

            


            

              

                
                
              

              
Checking…

            


            

              
              

                Retrieves chunks from TwymAtlas (MCP), then synthesizes a short demo answer via LiteLLM.
              

              
              
            

            
            

            

              
              
    
                
  1. Start TwymAtlas and open its MCP page (status must be Active).
    2. 
                
  2. Copy the MCP URL and API key exactly from that page into Fabric .env (ATLAS_MCP_URL, ATLAS_API_KEY), then restart Fabric.
    3. 
                
  3. If Atlas UI shows a different origin (e.g. :8080), either open Atlas on :8000 or set ATLAS_MCP_URL to that origin’s /mcp/ URL.
    4. 
                
  4. After Reconfigure / Revoke on Atlas MCP, you must paste the new tf_… key into Fabric .env — old keys return 401.
    5. 
                
  5. Use a knowledge agent (seeded: agt_ops_knowledge) or any agent with tool knowledge_search.
    6. 
                
  6. 
                  Via project: open
                  Twym Ops → map a knowledge agent → Execute
                  (pass agentId if multiple agents) with a message like “search knowledge for onboarding policy”.
                
    7. 
                
  7. 
                  Direct test:
                  Query Tester on Ops Knowledge Specialist.
                
    8. 
                
  8. If Atlas returned chunks, the execute response includes citations / knowledgeUsed: true.
    9. 
              

            

          

        

      


      
      

        

          

            

              
Route not found

              
That AI Services path is not configured.

            

            Back to agents