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

Yes. Write a rule that allows only the read operations the agent needs, such as reading customers and house-account balances, so it can review accounts without posting transactions. Posting a house-account transaction is a separate write operation that is not included unless you add it, and every call the agent makes is logged.

What authentication does the PocketPass API use?

The PocketPass API authenticates with a bearer API key sent in the Authorization header per its OpenAPI spec, and each key is scoped to a single merchant. Through Jentic the key is stored encrypted by your own instance and injected at call time, so it never appears in the agent's prompt or logs.

Can I post a transaction to a customer's house account with the PocketPass API?

Yes. You read the customer's house-account balance summary, then call the post-transaction operation to record a charge or credit against that account. You can list the account's transaction history, which is cursor-paginated, to confirm the posting.

What are the rate limits for the PocketPass API?

The OpenAPI spec does not specify rate limits for the PocketPass API. For current limits and key details, see the PocketPass documentation at https://pocketpass.golf.

How do I post a house-account charge through Jentic?

Import the PocketPass API from the Jentic API Directory, then have your agent issue a request such as 'post a charge to this golfer's house account'. Jentic matches the intent to the post-transaction operation and returns its input schema so the agent supplies the customer id and amount correctly, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.