Foxit PDF Services API vs iLoveAPI

Foxit PDF Services API

One credit per successful request, with failed calls, uploads, polling and downloads free, and a 500-credit yearly free plan. Access has no scopes, and the official MCP server reads and writes any local path. The status page has no component for the API, and no changelog was found.

iLoveAPI

Per-tool credit costs are public, 2,500 free credits arrive each month on a sign-up that asks for no card, and five official libraries are MIT. No OpenAPI file, status page or published rate-limit numbers were found, and the governing terms date from 14 February 2017.

Foxit PDF Services API

1. Exchange the client ID and secret at https://na1.fusion.foxit.com/oauth/token and cache the Bearer token. expires_in is about 24 hours and there is no refresh token
2. Upload first with POST /pdf-services/api/documents/upload, start the operation, poll GET /pdf-services/api/tasks/{task-id} until COMPLETED, then download resultDocumentId
3. Read the body of a 429. It means either the rate limit (15 a minute in sandbox, 100 in production) or QUOTA_EXCEEDED when credits run out
4. Keep uploads under 100 MB, and delete documents with DELETE /pdf-services/api/documents/{document-id} when done. Deletion is permanent
5. With the MCP server, pass only paths the task needs. upload_document reads any file:// path and download_document writes to any absolute path

iLoveAPI

1. Run four calls per job. GET /v1/start/{tool}/{region} returns a server and a task, then send upload, process and download to that server
2. Sign a JWT with the project secret key and send it as Authorization: Bearer. Tokens expire after one hour
3. Download results promptly. The reference says files are deleted one to two hours after processing, depending on tier
4. Back off exponentially on 429 and read the rate-limit headers on each response. No limit numbers are published
5. Add debug=true to any request to have the server echo the parameters without processing or spending credits