Can I check if json is spam with the SpamCheckAI: Spam Filter API?

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

What are the rate limits for the SpamCheckAI: Spam Filter 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 check if json is spam through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check if json is spam'. Jentic returns the matching SpamCheckAI: Spam Filter API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the SpamCheckAI: Spam Filter API have?

The SpamCheckAI: Spam Filter API exposes 4 endpoints covering spam, spam_reports operations.

Can I limit what my agent is allowed to do with the SpamCheckAI: Spam Filter API?

Yes. Because you run Jentic One yourself, you decide which SpamCheckAI operations your agent may call, so you can grant only checking content for spam and listing spam reports while leaving out creating or deleting spam reports. SpamCheckAI targets travel in the request body and query rather than in a resource path, so scoping happens at the operation level: an operation the agent has not been given is simply unavailable to it. This means a destructive call like deleting a spam report is never reachable unless you add it to the agent's allowed set.