Integration flow

The first developer integration should be narrow and easy to verify.

Step 1: Connect the service

The developer connects one MCP/API endpoint or one hosted skill.

The configuration should include:

• Service name.
• Tool list.
• Input and output expectations.
• Health check.
• Authentication method if needed.

Step 2: Define pricing

The developer defines how usage is charged.

Start with simple models:

• Per call.
• Per task.
• Free trial.
• Rate limit.

Avoid complex marketplace pricing in the first version. The goal is to prove that paid agent calls can be controlled and audited.

Step 3: Bind a payment rail

The developer binds the rail they want to use.

JiesdaPay should record the rail and the payment event, but does not need to custody funds in the first phase.

Step 4: Publish access

JiesdaPay publishes a paid endpoint or hosted skill address.

Agent runtimes can call this endpoint. JiesdaPay evaluates policy, budget, approval, and audit around the call.

Step 5: Review usage

The developer reviews:

• Call volume.
• Successful calls.
• Failed calls.
• Payment events.
• Revenue summaries.
• Webhook delivery.

This closes the loop from useful capability to paid agent-native service.