Agent Connection
Learn about connecting agents built with supported platforms to Pactory
Agent Connection Process
Connecting your agent to Pactory involves first creating it using one of our supported platforms, then connecting it through our integration process. Here’s what you’ll need to do:
Step 1: Choose Integration
Choose the platform where you’ll build your agent:
- FlowiseAI - Low-Code AI Builder
- LangFlow - Low-Code AI Builder
- ChatBotKit - No-Code AI Builder
- Beamlit - No-Code AI builder
- Relevance AI - No-Code AI builder
- n8n - No-Code AI builder
- Voker - No-Code AI builder
- Custom API - Custom API
Step 2: Integration Configuration
Required Fields
- Name: Enter your agent’s name
- Description: Provide a description of your agent’s functionality
- Input Placeholder: Add a helpful prompt that guides users on what to input
- API Connection Details: Enter the API keys and endpoints from your chosen platform
Settings
- Privacy Setting: Public or Private
- Output Setting: Chatting or Predictions
- Trial Credits: On or Off
- File Attachments: Enable or disable file uploads from users
- Supported file categories: Documents, Images, Videos, Audio, Other
Agent Media Requirements
-
Avatar Image:
- Format: JPG, PNG
- Size: 400x400px (minimum)
-
Screenshots:
- Recommended: 3-5 screenshots
- Format: JPG, PNG
- Resolution: 1280x720px (minimum)
-
Demo Video:
- Format: MP4
- Duration: 30-180 seconds
- Resolution: 1280x720px (minimum)
All media files should be clear and accurately represent your agent’s functionality. Screenshots should highlight key features and user interactions.
Step 3: Pricing Configuration
- Input Credits Price Per Token: Set the cost for processing input text (in credits per token)
- Output Credits Price Per Token: Set the cost for generated responses (in credits per token)
For more details about pricing and monetization, see our Monetization Guide.
Step 4: Completion
Once created, you’ll receive:
- A confirmation message
- Your agent’s unique URL
- Options to share on social media
Some fields may be pre-configured or unavailable depending on your chosen integration platform. Refer to the specific integration documentation for platform-specific details.