Is there an Orca Scan MCP server?

You don't need an MCP server to give your agent the Orca Scan REST API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent can read and update sheet rows straight away, with no extra server to run and no tool definitions to load into the agent's context.

Can I limit what my agent is allowed to do with the Orca Scan REST API?

Yes. Because Orca Scan carries the sheet id in the URL path, you can write a rule that allows only the row read and row update operations on a single sheet, so the agent can log scans and adjust quantities for that sheet and touch nothing else, and every call it makes is logged.

What authentication does the Orca Scan REST API use?

The Orca Scan REST API authenticates with a bearer token in the Authorization header per its OpenAPI spec, and that token is your Orca Scan API key. Through Jentic the key is stored encrypted by your own instance and added to each request at call time, so it never appears in the agent's prompt or logs.

Can I record scanned barcodes into a sheet with the Orca Scan REST API?

Yes. The API adds rows to a sheet and updates an existing row when the same item is scanned again, so an agent can append each scan and keep quantities current. You can also read back every row on a sheet and review its change history.

What are the rate limits for the Orca Scan REST API?

The OpenAPI spec does not specify rate limits for the Orca Scan REST API. For current limits and fair-use guidance, see the Orca Scan API documentation at https://orcascan.com/docs.

How do I log a scanned item to Orca Scan through Jentic?

Import the Orca Scan REST API from the Jentic API Directory, then have your agent issue a request such as 'add a row to my parts sheet with this barcode'. Jentic matches the intent to the add-row operation and returns its input schema so the agent builds the correct request, with your stored API key injected at call time.