futurehouse-client 0.3.19.dev129__tar.gz → 0.3.20.dev55__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (33) hide show
  1. futurehouse_client-0.3.20.dev55/PKG-INFO +523 -0
  2. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/README.md +1 -1
  3. futurehouse_client-0.3.20.dev55/futurehouse_client/__init__.py +22 -0
  4. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client/clients/rest_client.py +282 -139
  5. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client/models/app.py +10 -0
  6. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client/models/rest.py +36 -0
  7. futurehouse_client-0.3.20.dev55/futurehouse_client/utils/__init__.py +0 -0
  8. futurehouse_client-0.3.20.dev55/futurehouse_client/version.py +21 -0
  9. futurehouse_client-0.3.20.dev55/futurehouse_client.egg-info/PKG-INFO +523 -0
  10. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client.egg-info/SOURCES.txt +2 -1
  11. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client.egg-info/requires.txt +5 -1
  12. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/pyproject.toml +11 -7
  13. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/tests/test_rest.py +105 -38
  14. futurehouse_client-0.3.19.dev129/PKG-INFO +0 -316
  15. futurehouse_client-0.3.19.dev129/futurehouse_client/__init__.py +0 -11
  16. futurehouse_client-0.3.19.dev129/futurehouse_client.egg-info/PKG-INFO +0 -316
  17. futurehouse_client-0.3.19.dev129/uv.lock +0 -2953
  18. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/LICENSE +0 -0
  19. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/docs/__init__.py +0 -0
  20. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/docs/client_notebook.ipynb +0 -0
  21. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client/clients/__init__.py +0 -0
  22. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client/clients/job_client.py +0 -0
  23. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client/models/__init__.py +0 -0
  24. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client/models/client.py +0 -0
  25. /futurehouse_client-0.3.19.dev129/futurehouse_client/utils/__init__.py → /futurehouse_client-0.3.20.dev55/futurehouse_client/py.typed +0 -0
  26. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client/utils/auth.py +0 -0
  27. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client/utils/general.py +0 -0
  28. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client/utils/module_utils.py +0 -0
  29. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client/utils/monitoring.py +0 -0
  30. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client.egg-info/dependency_links.txt +0 -0
  31. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/futurehouse_client.egg-info/top_level.txt +0 -0
  32. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/setup.cfg +0 -0
  33. {futurehouse_client-0.3.19.dev129 → futurehouse_client-0.3.20.dev55}/tests/test_client.py +0 -0
@@ -0,0 +1,523 @@
1
+ Metadata-Version: 2.4
2
+ Name: futurehouse-client
3
+ Version: 0.3.20.dev55
4
+ Summary: A client for interacting with endpoints of the FutureHouse service.
5
+ Author-email: FutureHouse technical staff <hello@futurehouse.org>
6
+ License: Apache License
7
+ Version 2.0, January 2004
8
+ http://www.apache.org/licenses/
9
+
10
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
11
+
12
+ 1. Definitions.
13
+
14
+ "License" shall mean the terms and conditions for use, reproduction,
15
+ and distribution as defined by Sections 1 through 9 of this document.
16
+
17
+ "Licensor" shall mean the copyright owner or entity authorized by
18
+ the copyright owner that is granting the License.
19
+
20
+ "Legal Entity" shall mean the union of the acting entity and all
21
+ other entities that control, are controlled by, or are under common
22
+ control with that entity. For the purposes of this definition,
23
+ "control" means (i) the power, direct or indirect, to cause the
24
+ direction or management of such entity, whether by contract or
25
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
26
+ outstanding shares, or (iii) beneficial ownership of such entity.
27
+
28
+ "You" (or "Your") shall mean an individual or Legal Entity
29
+ exercising permissions granted by this License.
30
+
31
+ "Source" form shall mean the preferred form for making modifications,
32
+ including but not limited to software source code, documentation
33
+ source, and configuration files.
34
+
35
+ "Object" form shall mean any form resulting from mechanical
36
+ transformation or translation of a Source form, including but
37
+ not limited to compiled object code, generated documentation,
38
+ and conversions to other media types.
39
+
40
+ "Work" shall mean the work of authorship, whether in Source or
41
+ Object form, made available under the License, as indicated by a
42
+ copyright notice that is included in or attached to the work
43
+ (an example is provided in the Appendix below).
44
+
45
+ "Derivative Works" shall mean any work, whether in Source or Object
46
+ form, that is based on (or derived from) the Work and for which the
47
+ editorial revisions, annotations, elaborations, or other modifications
48
+ represent, as a whole, an original work of authorship. For the purposes
49
+ of this License, Derivative Works shall not include works that remain
50
+ separable from, or merely link (or bind by name) to the interfaces of,
51
+ the Work and Derivative Works thereof.
52
+
53
+ "Contribution" shall mean any work of authorship, including
54
+ the original version of the Work and any modifications or additions
55
+ to that Work or Derivative Works thereof, that is intentionally
56
+ submitted to Licensor for inclusion in the Work by the copyright owner
57
+ or by an individual or Legal Entity authorized to submit on behalf of
58
+ the copyright owner. For the purposes of this definition, "submitted"
59
+ means any form of electronic, verbal, or written communication sent
60
+ to the Licensor or its representatives, including but not limited to
61
+ communication on electronic mailing lists, source code control systems,
62
+ and issue tracking systems that are managed by, or on behalf of, the
63
+ Licensor for the purpose of discussing and improving the Work, but
64
+ excluding communication that is conspicuously marked or otherwise
65
+ designated in writing by the copyright owner as "Not a Contribution."
66
+
67
+ "Contributor" shall mean Licensor and any individual or Legal Entity
68
+ on behalf of whom a Contribution has been received by Licensor and
69
+ subsequently incorporated within the Work.
70
+
71
+ 2. Grant of Copyright License. Subject to the terms and conditions of
72
+ this License, each Contributor hereby grants to You a perpetual,
73
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
74
+ copyright license to reproduce, prepare Derivative Works of,
75
+ publicly display, publicly perform, sublicense, and distribute the
76
+ Work and such Derivative Works in Source or Object form.
77
+
78
+ 3. Grant of Patent License. Subject to the terms and conditions of
79
+ this License, each Contributor hereby grants to You a perpetual,
80
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
81
+ (except as stated in this section) patent license to make, have made,
82
+ use, offer to sell, sell, import, and otherwise transfer the Work,
83
+ where such license applies only to those patent claims licensable
84
+ by such Contributor that are necessarily infringed by their
85
+ Contribution(s) alone or by combination of their Contribution(s)
86
+ with the Work to which such Contribution(s) was submitted. If You
87
+ institute patent litigation against any entity (including a
88
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
89
+ or a Contribution incorporated within the Work constitutes direct
90
+ or contributory patent infringement, then any patent licenses
91
+ granted to You under this License for that Work shall terminate
92
+ as of the date such litigation is filed.
93
+
94
+ 4. Redistribution. You may reproduce and distribute copies of the
95
+ Work or Derivative Works thereof in any medium, with or without
96
+ modifications, and in Source or Object form, provided that You
97
+ meet the following conditions:
98
+
99
+ (a) You must give any other recipients of the Work or
100
+ Derivative Works a copy of this License; and
101
+
102
+ (b) You must cause any modified files to carry prominent notices
103
+ stating that You changed the files; and
104
+
105
+ (c) You must retain, in the Source form of any Derivative Works
106
+ that You distribute, all copyright, patent, trademark, and
107
+ attribution notices from the Source form of the Work,
108
+ excluding those notices that do not pertain to any part of
109
+ the Derivative Works; and
110
+
111
+ (d) If the Work includes a "NOTICE" text file as part of its
112
+ distribution, then any Derivative Works that You distribute must
113
+ include a readable copy of the attribution notices contained
114
+ within such NOTICE file, excluding those notices that do not
115
+ pertain to any part of the Derivative Works, in at least one
116
+ of the following places: within a NOTICE text file distributed
117
+ as part of the Derivative Works; within the Source form or
118
+ documentation, if provided along with the Derivative Works; or,
119
+ within a display generated by the Derivative Works, if and
120
+ wherever such third-party notices normally appear. The contents
121
+ of the NOTICE file are for informational purposes only and
122
+ do not modify the License. You may add Your own attribution
123
+ notices within Derivative Works that You distribute, alongside
124
+ or as an addendum to the NOTICE text from the Work, provided
125
+ that such additional attribution notices cannot be construed
126
+ as modifying the License.
127
+
128
+ You may add Your own copyright statement to Your modifications and
129
+ may provide additional or different license terms and conditions
130
+ for use, reproduction, or distribution of Your modifications, or
131
+ for any such Derivative Works as a whole, provided Your use,
132
+ reproduction, and distribution of the Work otherwise complies with
133
+ the conditions stated in this License.
134
+
135
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
136
+ any Contribution intentionally submitted for inclusion in the Work
137
+ by You to the Licensor shall be under the terms and conditions of
138
+ this License, without any additional terms or conditions.
139
+ Notwithstanding the above, nothing herein shall supersede or modify
140
+ the terms of any separate license agreement you may have executed
141
+ with Licensor regarding such Contributions.
142
+
143
+ 6. Trademarks. This License does not grant permission to use the trade
144
+ names, trademarks, service marks, or product names of the Licensor,
145
+ except as required for reasonable and customary use in describing the
146
+ origin of the Work and reproducing the content of the NOTICE file.
147
+
148
+ 7. Disclaimer of Warranty. Unless required by applicable law or
149
+ agreed to in writing, Licensor provides the Work (and each
150
+ Contributor provides its Contributions) on an "AS IS" BASIS,
151
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
152
+ implied, including, without limitation, any warranties or conditions
153
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
154
+ PARTICULAR PURPOSE. You are solely responsible for determining the
155
+ appropriateness of using or redistributing the Work and assume any
156
+ risks associated with Your exercise of permissions under this License.
157
+
158
+ 8. Limitation of Liability. In no event and under no legal theory,
159
+ whether in tort (including negligence), contract, or otherwise,
160
+ unless required by applicable law (such as deliberate and grossly
161
+ negligent acts) or agreed to in writing, shall any Contributor be
162
+ liable to You for damages, including any direct, indirect, special,
163
+ incidental, or consequential damages of any character arising as a
164
+ result of this License or out of the use or inability to use the
165
+ Work (including but not limited to damages for loss of goodwill,
166
+ work stoppage, computer failure or malfunction, or any and all
167
+ other commercial damages or losses), even if such Contributor
168
+ has been advised of the possibility of such damages.
169
+
170
+ 9. Accepting Warranty or Additional Liability. While redistributing
171
+ the Work or Derivative Works thereof, You may choose to offer,
172
+ and charge a fee for, acceptance of support, warranty, indemnity,
173
+ or other liability obligations and/or rights consistent with this
174
+ License. However, in accepting such obligations, You may act only
175
+ on Your own behalf and on Your sole responsibility, not on behalf
176
+ of any other Contributor, and only if You agree to indemnify,
177
+ defend, and hold each Contributor harmless for any liability
178
+ incurred by, or claims asserted against, such Contributor by reason
179
+ of your accepting any such warranty or additional liability.
180
+
181
+ END OF TERMS AND CONDITIONS
182
+
183
+ APPENDIX: How to apply the Apache License to your work.
184
+
185
+ To apply the Apache License to your work, attach the following
186
+ boilerplate notice, with the fields enclosed by brackets "[]"
187
+ replaced with your own identifying information. (Don't include
188
+ the brackets!) The text should be enclosed in the appropriate
189
+ comment syntax for the file format. We also recommend that a
190
+ file or class name and description of purpose be included on the
191
+ same "printed page" as the copyright notice for easier
192
+ identification within third-party archives.
193
+
194
+ Copyright 2024 FutureHouse
195
+
196
+ Licensed under the Apache License, Version 2.0 (the "License");
197
+ you may not use this file except in compliance with the License.
198
+ You may obtain a copy of the License at
199
+
200
+ http://www.apache.org/licenses/LICENSE-2.0
201
+
202
+ Unless required by applicable law or agreed to in writing, software
203
+ distributed under the License is distributed on an "AS IS" BASIS,
204
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
205
+ See the License for the specific language governing permissions and
206
+ limitations under the License.
207
+
208
+ Classifier: Operating System :: OS Independent
209
+ Classifier: Programming Language :: Python :: 3 :: Only
210
+ Classifier: Programming Language :: Python :: 3.11
211
+ Classifier: Programming Language :: Python :: 3.12
212
+ Classifier: Programming Language :: Python
213
+ Requires-Python: <3.14,>=3.11
214
+ Description-Content-Type: text/markdown
215
+ License-File: LICENSE
216
+ Requires-Dist: cloudpickle
217
+ Requires-Dist: fhaviary
218
+ Requires-Dist: httpx
219
+ Requires-Dist: ldp>=0.22.0
220
+ Requires-Dist: litellm==1.67.4.post1
221
+ Requires-Dist: pydantic
222
+ Requires-Dist: python-dotenv
223
+ Requires-Dist: tenacity
224
+ Requires-Dist: tqdm>=4.62
225
+ Provides-Extra: dev
226
+ Requires-Dist: black; extra == "dev"
227
+ Requires-Dist: futurehouse-client[monitoring,typing]; extra == "dev"
228
+ Requires-Dist: jupyter; extra == "dev"
229
+ Requires-Dist: jupyterlab; extra == "dev"
230
+ Requires-Dist: mypy; extra == "dev"
231
+ Requires-Dist: notebook; extra == "dev"
232
+ Requires-Dist: pre-commit; extra == "dev"
233
+ Requires-Dist: pylint; extra == "dev"
234
+ Requires-Dist: pylint-per-file-ignores; extra == "dev"
235
+ Requires-Dist: pylint-pydantic; extra == "dev"
236
+ Requires-Dist: pytest; extra == "dev"
237
+ Requires-Dist: pytest-asyncio; extra == "dev"
238
+ Requires-Dist: pytest-rerunfailures; extra == "dev"
239
+ Requires-Dist: pytest-subtests; extra == "dev"
240
+ Requires-Dist: pytest-timeout; extra == "dev"
241
+ Requires-Dist: pytest-xdist; extra == "dev"
242
+ Requires-Dist: ruff; extra == "dev"
243
+ Requires-Dist: setuptools_scm; extra == "dev"
244
+ Provides-Extra: monitoring
245
+ Requires-Dist: newrelic>=8.8.0; extra == "monitoring"
246
+ Provides-Extra: typing
247
+ Requires-Dist: types-requests; extra == "typing"
248
+ Requires-Dist: types-tqdm; extra == "typing"
249
+ Dynamic: license-file
250
+
251
+ # FutureHouse Platform API Documentation
252
+
253
+ Documentation and tutorials for futurehouse-client, a client for interacting with endpoints of the FutureHouse platform.
254
+
255
+ <!--TOC-->
256
+
257
+ - [Installation](#installation)
258
+ - [Quickstart](#quickstart)
259
+ - [Functionalities](#functionalities)
260
+ - [Authentication](#authentication)
261
+ - [Simple task running](#simple-task-running)
262
+ - [Task Continuation](#task-continuation)
263
+ - [Asynchronous tasks](#asynchronous-tasks)
264
+
265
+ <!--TOC-->
266
+
267
+ ## Installation
268
+
269
+ ```bash
270
+ uv pip install futurehouse-client
271
+ ```
272
+
273
+ ## Quickstart
274
+
275
+ ```python
276
+ from futurehouse_client import FutureHouseClient, JobNames
277
+ from pathlib import Path
278
+ from aviary.core import DummyEnv
279
+ import ldp
280
+
281
+ client = FutureHouseClient(
282
+ api_key="your_api_key",
283
+ )
284
+
285
+ task_data = {
286
+ "name": JobNames.CROW,
287
+ "query": "Which neglected diseases had a treatment developed by artificial intelligence?",
288
+ }
289
+
290
+ task_response = client.run_tasks_until_done(task_data)
291
+ ```
292
+
293
+ A quickstart example can be found in the [client_notebook.ipynb](https://futurehouse.gitbook.io/futurehouse-cookbook/futurehouse-client/docs/client_notebook) file, where we show how to submit and retrieve a job task, pass runtime configuration to the agent, and ask follow-up questions to the previous job.
294
+
295
+ ## Functionalities
296
+
297
+ FutureHouse client implements a RestClient (called `FutureHouseClient`) with the following functionalities:
298
+
299
+ - [Simple task running](#simple-task-running): `run_tasks_until_done(TaskRequest)` or `await arun_tasks_until_done(TaskRequest)`
300
+ - [Asynchronous tasks](#asynchronous-tasks): `get_task(task_id)` or `aget_task(task_id)` and `create_task(TaskRequest)` or `acreate_task(TaskRequest)`
301
+
302
+ To create a `FutureHouseClient`, you need to pass an FutureHouse platform api key (see [Authentication](#authentication)):
303
+
304
+ ```python
305
+ from futurehouse_client import FutureHouseClient
306
+
307
+ client = FutureHouseClient(
308
+ api_key="your_api_key",
309
+ )
310
+ ```
311
+
312
+ ## Authentication
313
+
314
+ In order to use the `FutureHouseClient`, you need to authenticate yourself. Authentication is done by providing an API key, which can be obtained directly from your [profile page in the FutureHouse platform](https://platform.futurehouse.org/profile).
315
+
316
+ ## Simple task running
317
+
318
+ In the FutureHouse platform, we define the deployed combination of an agent and an environment as a `job`. To invoke a job, we need to submit a `task` (also called a `query`) to it.
319
+ `FutureHouseClient` can be used to submit tasks/queries to available jobs in the FutureHouse platform. Using a `FutureHouseClient` instance, you can submit tasks to the platform by calling the `create_task` method, which receives a `TaskRequest` (or a dictionary with `kwargs`) and returns the task id.
320
+ Aiming to make the submission of tasks as simple as possible, we have created a `JobNames` `enum` that contains the available task types.
321
+
322
+ The available supported jobs are:
323
+ | Alias | Job Name | Task type | Description |
324
+ | --- | --- | --- | --- |
325
+ | `JobNames.CROW` | `job-futurehouse-paperqa2` | Fast Search | Ask a question of scientific data sources, and receive a high-accuracy, cited response. Built with [PaperQA2](https://github.com/Future-House/paper-qa). |
326
+ | `JobNames.FALCON` | `job-futurehouse-paperqa2-deep` | Deep Search | Use a plethora of sources to deeply research. Receive a detailed, structured report as a response. |
327
+ | `JobNames.OWL` | `job-futurehouse-hasanyone` | Precedent Search | Formerly known as HasAnyone, query if anyone has ever done something in science. |
328
+ | `JobNames.PHOENIX` | `job-futurehouse-phoenix` | Chemistry Tasks | A new iteration of ChemCrow, Phoenix uses cheminformatics tools to do chemistry. Good for planning synthesis and designing new molecules. |
329
+ | `JobNames.DUMMY` | `job-futurehouse-dummy` | Dummy Task | This is a dummy task. Mainly for testing purposes. |
330
+
331
+ Using `JobNames`, the task submission looks like this:
332
+
333
+ ```python
334
+ from futurehouse_client import FutureHouseClient, JobNames
335
+
336
+ client = FutureHouseClient(
337
+ api_key="your_api_key",
338
+ )
339
+
340
+ task_data = {
341
+ "name": JobNames.OWL,
342
+ "query": "Has anyone tested therapeutic exerkines in humans or NHPs?",
343
+ }
344
+
345
+ task_response = client.run_tasks_until_done(task_data)
346
+
347
+ print(task_response.answer)
348
+ ```
349
+
350
+ Or if running async code:
351
+
352
+ ```python
353
+ import asyncio
354
+ from futurehouse_client import FutureHouseClient, JobNames
355
+
356
+
357
+ async def main():
358
+ client = FutureHouseClient(
359
+ api_key="your_api_key",
360
+ )
361
+
362
+ task_data = {
363
+ "name": JobNames.OWL,
364
+ "query": "Has anyone tested therapeutic exerkines in humans or NHPs?",
365
+ }
366
+
367
+ task_response = await client.arun_tasks_until_done(task_data)
368
+ print(task_response.answer)
369
+ return task_id
370
+
371
+
372
+ # For Python 3.7+
373
+ if __name__ == "__main__":
374
+ task_id = asyncio.run(main())
375
+ ```
376
+
377
+ Note that in either the sync or the async code, collections of tasks can be given to the client to run them in a batch:
378
+
379
+ ```python
380
+ import asyncio
381
+ from futurehouse_client import FutureHouseClient, JobNames
382
+
383
+
384
+ async def main():
385
+ client = FutureHouseClient(
386
+ api_key="your_api_key",
387
+ )
388
+
389
+ task_data = [
390
+ {
391
+ "name": JobNames.OWL,
392
+ "query": "Has anyone tested therapeutic exerkines in humans or NHPs?",
393
+ },
394
+ {
395
+ "name": JobNames.CROW,
396
+ "query": "Are there any clinically validated therapeutic exerkines for humans?",
397
+ },
398
+ ]
399
+
400
+ task_responses = await client.arun_tasks_until_done(task_data)
401
+ print(task_responses[0].answer)
402
+ print(task_responses[1].answer)
403
+ return task_id
404
+
405
+
406
+ # For Python 3.7+
407
+ if __name__ == "__main__":
408
+ task_id = asyncio.run(main())
409
+ ```
410
+
411
+ `TaskRequest` can also be used to submit jobs and it has the following fields:
412
+
413
+ | Field | Type | Description |
414
+ | -------------- | ------------- | ------------------------------------------------------------------------------------------------------------------- |
415
+ | id | UUID | Optional job identifier. A UUID will be generated if not provided |
416
+ | name | str | Name of the job to execute eg. `job-futurehouse-paperqa2`, or using the `JobNames` for convenience: `JobNames.CROW` |
417
+ | query | str | Query or task to be executed by the job |
418
+ | runtime_config | RuntimeConfig | Optional runtime parameters for the job |
419
+
420
+ `runtime_config` can receive a `AgentConfig` object with the desired kwargs. Check the available `AgentConfig` fields in the [LDP documentation](https://github.com/Future-House/ldp/blob/main/src/ldp/agent/agent.py#L87). Besides the `AgentConfig` object, we can also pass `timeout` and `max_steps` to limit the execution time and the number of steps the agent can take.
421
+
422
+ ```python
423
+ from futurehouse_client import FutureHouseClient, JobNames
424
+ from futurehouse_client.models.app import TaskRequest
425
+
426
+ client = FutureHouseClient(
427
+ api_key="your_api_key",
428
+ )
429
+
430
+ task_response = client.run_tasks_until_done(
431
+ TaskRequest(
432
+ name=JobNames.OWL,
433
+ query="Has anyone tested therapeutic exerkines in humans or NHPs?",
434
+ )
435
+ )
436
+
437
+ print(task_response.answer)
438
+ ```
439
+
440
+ A `TaskResponse` will be returned from using our agents. For Owl, Crow, and Falcon, we default to a subclass, `PQATaskResponse` which has some key attributes:
441
+
442
+ | Field | Type | Description |
443
+ | --------------------- | ---- | ------------------------------------------------------------------------------- |
444
+ | answer | str | Answer to your query. |
445
+ | formatted_answer | str | Specially formatted answer with references. |
446
+ | has_successful_answer | bool | Flag for whether the agent was able to find a good answer to your query or not. |
447
+
448
+ If using the `verbose` setting, much more data can be pulled down from your `TaskResponse`, which will exist across all agents (not just Owl, Crow, and Falcon).
449
+
450
+ ```python
451
+ from futurehouse_client import FutureHouseClient, JobNames
452
+ from futurehouse_client.models.app import TaskRequest
453
+
454
+ client = FutureHouseClient(
455
+ api_key="your_api_key",
456
+ )
457
+
458
+ task_response = client.run_tasks_until_done(
459
+ TaskRequest(
460
+ name=JobNames.OWL,
461
+ query="Has anyone tested therapeutic exerkines in humans or NHPs?",
462
+ ),
463
+ verbose=True,
464
+ )
465
+
466
+ print(task_response.environment_frame)
467
+ ```
468
+
469
+ In that case, a `TaskResponseVerbose` will have the following fields:
470
+
471
+ | Field | Type | Description |
472
+ | ----------------- | ---- | ---------------------------------------------------------------------------------------------------------------------- | --- |
473
+ | agent_state | dict | Large object with all agent states during the progress of your task. |
474
+ | environment_frame | dict | Large nested object with all environment data, for PQA environments it includes contexts, paper metadata, and answers. |
475
+ | metadata | dict | Extra metadata about your query. | |
476
+
477
+ ## Task Continuation
478
+
479
+ Once a task is submitted and the answer is returned, FutureHouse platform allow you to ask follow-up questions to the previous task.
480
+ It is also possible through the platform API.
481
+ To accomplish that, we can use the `runtime_config` we discussed in the [Simple task running](#simple-task-running) section.
482
+
483
+ ```python
484
+ from futurehouse_client import FutureHouseClient, JobNames
485
+
486
+ client = FutureHouseClient(
487
+ api_key="your_api_key",
488
+ )
489
+
490
+ task_data = {"name": JobNames.CROW, "query": "How many species of birds are there?"}
491
+
492
+ task_id = client.create_task(task_data)
493
+
494
+ continued_task_data = {
495
+ "name": JobNames.CROW,
496
+ "query": "From the previous answer, specifically,how many species of crows are there?",
497
+ "runtime_config": {"continued_task_id": task_id},
498
+ }
499
+
500
+ task_result = client.run_tasks_until_done(continued_task_data)
501
+ ```
502
+
503
+ ## Asynchronous tasks
504
+
505
+ Sometimes you may want to submit many jobs, while querying results at a later time. In this way you can do other things while waiting for a response. The platform API supports this as well rather than waiting for a result.
506
+
507
+ ```python
508
+ from futurehouse_client import FutureHouseClient
509
+
510
+ client = FutureHouseClient(
511
+ api_key="your_api_key",
512
+ )
513
+
514
+ task_data = {"name": JobNames.CROW, "query": "How many species of birds are there?"}
515
+
516
+ task_id = client.create_task(task_data)
517
+
518
+ # move on to do other things
519
+
520
+ task_status = client.get_task(task_id)
521
+ ```
522
+
523
+ `task_status` contains information about the task. For instance, its `status`, `task`, `environment_name` and `agent_name`, and other fields specific to the job. You can continually query the status until it's `success` before moving on.
@@ -75,7 +75,7 @@ The available supported jobs are:
75
75
  | `JobNames.CROW` | `job-futurehouse-paperqa2` | Fast Search | Ask a question of scientific data sources, and receive a high-accuracy, cited response. Built with [PaperQA2](https://github.com/Future-House/paper-qa). |
76
76
  | `JobNames.FALCON` | `job-futurehouse-paperqa2-deep` | Deep Search | Use a plethora of sources to deeply research. Receive a detailed, structured report as a response. |
77
77
  | `JobNames.OWL` | `job-futurehouse-hasanyone` | Precedent Search | Formerly known as HasAnyone, query if anyone has ever done something in science. |
78
- | `JobNames.PHOENIX` | `job-futurehouse-phoenix` | Chemistry Tasks | A new iteration of ChemCrow, Phoenix uses cheminformatics tools to do chemistry. Good for planning synthesis and design of new molecules. |
78
+ | `JobNames.PHOENIX` | `job-futurehouse-phoenix` | Chemistry Tasks | A new iteration of ChemCrow, Phoenix uses cheminformatics tools to do chemistry. Good for planning synthesis and designing new molecules. |
79
79
  | `JobNames.DUMMY` | `job-futurehouse-dummy` | Dummy Task | This is a dummy task. Mainly for testing purposes. |
80
80
 
81
81
  Using `JobNames`, the task submission looks like this:
@@ -0,0 +1,22 @@
1
+ from .clients.job_client import JobClient, JobNames
2
+ from .clients.rest_client import RestClient as FutureHouseClient
3
+ from .models.app import (
4
+ FinchTaskResponse,
5
+ PhoenixTaskResponse,
6
+ PQATaskResponse,
7
+ TaskRequest,
8
+ TaskResponse,
9
+ TaskResponseVerbose,
10
+ )
11
+
12
+ __all__ = [
13
+ "FinchTaskResponse",
14
+ "FutureHouseClient",
15
+ "JobClient",
16
+ "JobNames",
17
+ "PQATaskResponse",
18
+ "PhoenixTaskResponse",
19
+ "TaskRequest",
20
+ "TaskResponse",
21
+ "TaskResponseVerbose",
22
+ ]