ProvelyNo. OpenAI Platform API returns a success response when it accepts the request. Provely proves all_requests_succeeded, completed and succeeded as separate promises.
| Fact | Value |
|---|---|
| Skill version | 0.1.0 |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Last conformance run | 2026-09-05T12:00:00Z: 41 of 41 cases passed, 0 critical false VERIFIED |
| Provider API versions | spec_2_3_0 |
| Default provider API version | spec_2_3_0 |
| Compiled | 2026-09-05 |
| Manifest hash | 43f3e094fd9eea85 |
| Manifest hash check | the document hashes to the value the manifest states |
| Signature | valid, key provely-skill-2026-09, trusted by this build |
What does this page prove?
| Claim | Proven by | Evidence | Status |
|---|---|---|---|
| A batch that reaches the status completed is not a batch in which every request succeeded. This level reads request_counts and refuses a batch with a failed count above zero. | openai.batch.all_requests_succeeded | E2 + E3 | proven |
| The provider ran the batch and the results are ready. This level does not prove that every request inside the batch succeeded. Read openai.batch.all_requests_succeeded for that promise. | openai.batch.completed | E2 + E3 | proven |
| The job reached the status succeeded and the member fine_tuned_model holds a name. The level does not prove that the model answers a request. No published operation states that. | openai.fine_tuning_job.succeeded | E2 + E3 | proven |
| An outcome outside OpenAI Platform API, such as a bank credit or a person who read a message | not proven | no E5 channel | not proven |
| The agent report that the action worked | never counts | E0 | not proven |
Which completion levels does the OpenAI Platform API skill expose?
Each level is one promise with one contract. An agent picks the level that matches the promise it makes. It cannot upgrade a level. Read the completion level definition.
| Level | Contract | Promise | Evidence | Certification |
|---|---|---|---|---|
all_requests_succeeded | openai.batch.all_requests_succeeded v1.0.0 | A batch that reaches the status completed is not a batch in which every request succeeded. This level reads request_counts and refuses a batch with a failed count above zero. | E2 + E3 | Provisional |
completed | openai.batch.completed v1.0.0 | The provider ran the batch and the results are ready. This level does not prove that every request inside the batch succeeded. Read openai.batch.all_requests_succeeded for that promise. | E2 + E3 | Provisional |
succeeded | openai.fine_tuning_job.succeeded v1.0.0 | The job reached the status succeeded and the member fine_tuned_model holds a name. The level does not prove that the model answers a request. No published operation states that. | E2 + E3 | Provisional |
Which ways can a OpenAI Platform API action look done and not be?
| Contract | Case | Verdict |
|---|---|---|
| openai.batch.all_requests_succeeded | partial completion | CONTRADICTED |
| openai.batch.all_requests_succeeded | pre existing state | CONTRADICTED |
| openai.batch.all_requests_succeeded | wrong subject | CONTRADICTED |
| openai.batch.completed | pre existing state | CONTRADICTED |
| openai.batch.completed | wrong subject | CONTRADICTED |
| openai.fine_tuning_job.succeeded | pre existing state | CONTRADICTED |
| openai.fine_tuning_job.succeeded | wrong subject | CONTRADICTED |
What did the last conformance run show?
The last conformance run on 2026-09-05T12:00:00Z passed 41 of 41 cases with 0 critical false VERIFIED. One critical false VERIFIED rejects a skill.
| Contract | Certification |
|---|---|
openai.batch.all_requests_succeeded | Provisional |
openai.batch.completed | Provisional |
openai.fine_tuning_job.succeeded | Provisional |
The weakest contract is openai.batch.all_requests_succeeded. It reaches Provisional. The package level is Provisional, because a package level never rises above its weakest contract. Read the level of the contract you use.
| Case class | Passed | Total |
|---|---|---|
| error after execution | 3 | 3 |
| error before execution | 3 | 3 |
| evidence unavailable | 3 | 3 |
| pre existing state | 3 | 3 |
| stale readback | 3 | 3 |
| still transitional | 3 | 3 |
| terminal failure | 3 | 3 |
| terminal success | 3 | 3 |
| timeout after commit | 3 | 3 |
| version mismatch | 3 | 3 |
| webhook duplicate | 3 | 3 |
| webhook out of order | 3 | 3 |
| wrong subject | 3 | 3 |
| wrong terminal state | 2 | 2 |
The conformance artifact digest is 5d615bdc87a754e5. The harness signs the run, so a reader can check that these numbers come from that run.
What remains uncertain?
The level is Provisional because of it. Provely does not guess a rule that a source does not state.
Where do these facts come from?
Every claim above cites a source assertion in the skill provenance. The compiler records the source, its hash, and the retrieval date. A page never states a provider rule without one.
| Source | Kind | Retrieved | Excerpt |
|---|---|---|---|
| openai.docs.batch | docs | 2026-09-09 | authored |
| openai.docs.fine_tuning | docs | 2026-09-09 | authored |
| openai.docs.versions | docs | 2026-09-09 | authored |
| openai.docs.webhooks | docs | 2026-09-09 | authored |
| openai.events | event sample | 2026-09-09 | authored |
| openai.openapi | openapi | 2026-09-09 | trimmed |
How do I verify a OpenAI Platform API action?
Verify a OpenAI Platform API action with Provely
- Begin the operation.Call
beginwith the contractopenai.batch.all_requests_succeededand the input. Keep the operation id. - Make the OpenAI Platform API call you make today.Send the request with the correlation metadata that
beginreturned. - Submit the acknowledgement.Call
action_resultwith the OpenAI Platform API response. This is evidence level E1. It is not completion. - Verify.Call
verify. The runtime reads the evidence that the contract names, from OpenAI Platform API and not from the agent, and evaluates the contract. - Report the verdict exactly as returned.VERIFIED comes with a signed receipt. PENDING comes with the operation id. CONTRADICTED and UNVERIFIABLE are not success.
Questions developers ask
Does the all_requests_succeeded level prove the succeeded level?
No. A batch that reaches the status completed is not a batch in which every request succeeded. This level reads request_counts and refuses a batch with a failed count above zero. The job reached the status succeeded and the member fine_tuned_model holds a name. The level does not prove that the model answers a request. No published operation states that. Use openai.fine_tuning_job.succeeded to prove succeeded.
What does the agent say while the OpenAI Platform API action is still in progress?
It says: "The action is accepted but not yet verified. Operation: <id>." The verdict is PENDING. The runtime observes again on the contract timing policy.
Which OpenAI Platform API API versions does the skill support?
spec_2_3_0. An operation on another version returns UNVERIFIABLE with the reason version_unsupported. The runtime never guesses.
Does Provely need write access to OpenAI Platform API?
No. The agent keeps its write key. The verifier reads with a separate read-only credential where OpenAI Platform API permits it, and it never shares that credential with the agent.