Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.stardeck.ai/llms.txt

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

This guide walks you through making a Point of Sale app callable by the Cofounder Agent. By the end, the Cofounder will be able to pull sales reports, check inventory, look up orders, and more — all through conversation.

​
Prerequisites

  • A POS app built on Stardeck with data you want to expose (products, orders, sales)
  • The app should be published to production or have a running sandbox

​
Step 1: Ask the Agent to Expose APIs

Open your POS app’s project chat and tell the agent what you want other apps to be able to do. You don’t need to specify routes, parameters, or technical details — the agent designs all of that. 
Set up APIs so the Cofounder Agent can check sales, look up orders,
and see inventory levels
Or even simpler: 
Expose an API so agents can use this app
The agent creates the endpoints, picks the right routes and parameters, and adds documentation so other agents know how to call them. The platform automatically detects and publishes the new endpoints once they’re built.
Start with read-only access. You can ask the agent to add write endpoints later once you’re comfortable with the flow.

​
Step 2: Test from the Project Chat

Before involving other apps, you can test your new endpoints right from the project chat. The project agent can make cross-app calls to your own app’s API: 
Test the sales endpoint and show me what it returns

Call the inventory endpoint and check if the data looks right
This lets you verify everything works before opening it up to the Cofounder Agent or other apps.

​
Step 3: Enable Cross-App Access

Go to your POS app’s Settings tab and open the Cross-App section. Option A: Allow all apps (quickest) Toggle on Allow all apps to call this project. This lets the Cofounder Agent (and any other app in the org) make GET requests to your POS endpoints. Since the endpoints are read-only, this works well. Option B: Explicit grant (more control) If you want to restrict access or allow write methods later, create an explicit grant instead. You’ll select which apps can call your POS app and which HTTP methods they’re allowed to use.

​
Configure Agent Environments

Under Agent Callable Environments, choose which environments the Cofounder Agent can target:
  • Sandbox only — good while you’re still building and testing endpoints
  • Both — once your endpoints are stable and you want the agent to query live production data

​
Step 4: Talk to the Cofounder

Open the Cofounder Agent from your organization dashboard. You can now ask it to query your POS app: Check today’s sales:
“How much revenue did the POS app make today?”
Investigate inventory:
“What products in the POS app are running low on stock?”
Look up a specific order:
“Look up order ORD-2847 in the POS app”
Get a business summary:
“Give me a sales summary from the POS app for last week — total revenue, number of orders, and average order value”
Cross-reference with another app:
“Compare this week’s POS sales to last week’s, and if revenue dropped more than 10%, create a task in the project management app to investigate”
The Cofounder Agent will discover the available endpoints, make the appropriate calls, and present the data back to you in the conversation.

​
Adding Write Access Later

Once you’re comfortable with read-only access, you can expand to write operations. Ask the project agent: 
Add write access so agents can also create orders and adjust inventory
Then create an explicit grant with the HTTP methods you want to allow, and the Cofounder can do things like “Add 50 units of SKU-1234 to the POS inventory” or “Create a sample order in the POS sandbox to test the checkout flow.”
Write access means the agent can modify data. Use sandbox-only for agent environments until you’re confident the endpoints have proper validation.