Public Images (Profile Images)
Public images are photos displayed on bot and user profiles. These are visible on the profile and can be referenced naturally in conversations.
Overview
- For Bots: Profile photos that users can see and browse on the bot's profile
- For Users: Profile photos that the bot can see and reference in conversations
- Recommended: 1-5+ photos per profile for the best experience
- Visibility: Always visible - displayed on profiles before and during conversations
Why Use Public Images?
Public images create a realistic dating experience. Users can browse photos before matching, and both the bot and user can reference photos naturally during conversation.
Managing Public Images
Through the Dashboard
You can upload and manage public images through the web dashboard at app.prioros.com.
Through the API
Upload a Public Image
POST /api/content
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
{
"bot_id": "550e8400-e29b-41d4-a716-446655440000",
"image_url": "https://example.com/profile-photo.jpg",
"public": true
}
For Users
POST /api/content
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
{
"user_id": "user_12345",
"image_url": "https://example.com/user-photo.jpg",
"public": true
}
How It Works in Conversations
When users browse a bot's profile and see photos, they can reference them naturally in conversation. The bot understands what's in its photos and responds accordingly.
The bot knows what's in its public photos and can discuss them naturally, just like a real person would.
How bots use user photos:
Bot: "You look great in that beach photo! Do you travel a lot?"
User: "Yeah I love the beach"
Bot: "I can tell! That sunset pic was amazing"
Bot: "I saw you have a dog in one of your pics, what breed?"
User: "He's a husky!"
Bot: "Aw cute! What's his name?"
The bot can naturally reference what it sees in user photos, making conversations feel more personal and realistic.
API Reference
List Content
Get all public images for a bot or user:
GET /api/content?bot_id=550e8400-e29b-41d4-a716-446655440000&public=true
Authorization: Bearer YOUR_API_KEY
Delete Content
DELETE /api/content/{content_id}
Authorization: Bearer YOUR_API_KEY