Can I confirm payment (결제 승인) with the Toss Payments API?

Yes. Use the POST /v1/payments/confirm endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Toss Payments API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I confirm payment (결제 승인) through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'confirm payment (결제 승인)'. Jentic returns the matching Toss Payments API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Toss Payments API have?

The Toss Payments API exposes 4 endpoints covering payments operations.

Can I limit what my agent is allowed to do with the Toss Payments API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Toss Payments operations and credentials your agent may use. You can pin the agent to just the calls it needs, such as confirming a payment with POST /v1/payments/confirm or reading one with GET /v1/payments/{paymentKey}, while leaving cancellation via POST /v1/payments/{paymentKey}/cancel off the allowed list unless you add it. Because the payment key sits in the URL path, the operator controls exactly which operations run against a given payment.